As we write custom WebAPI applications, we need to take extra steps to secure sensitive information after deployment. Below is one of the steps you can take to encrypt the web.config file, which is a popular place where configurable sensitive information is stored.
Powerpoint slide
Cheers!
Showing posts with label WebAPI. Show all posts
Showing posts with label WebAPI. Show all posts
Thursday, July 26, 2018
Monday, May 30, 2016
WebAPI connection exception Error Subset Found: Server error-00150-No response returned from the server
When writing a Colleague custom WebAPI, I encountered a connection error while executing a transaction:
I made sure my credential was correct and the connection was established before calling the transaction. After much debugging, I found out that the string that was passed to the transaction exceeded the size limit of a field in Colleague. I passed in a 15 character long string and tried to write it to a 10 character long field in Colleague through the transaction, and it resulted in a truncation error which ended the Colleague session. This also returned the error above. They do not look like they're related, so it was hard to track down. Make sure you check the size of the arguments of the transaction when you get these error.
[Ellucian.Data.Colleague.Exceptions.ColleagueTransactionException] = {"Error Subset Found: Server error-00150-No response returned from the server."}
I made sure my credential was correct and the connection was established before calling the transaction. After much debugging, I found out that the string that was passed to the transaction exceeded the size limit of a field in Colleague. I passed in a 15 character long string and tried to write it to a 10 character long field in Colleague through the transaction, and it resulted in a truncation error which ended the Colleague session. This also returned the error above. They do not look like they're related, so it was hard to track down. Make sure you check the size of the arguments of the transaction when you get these error.
Tuesday, January 19, 2016
How to add ColleagueSDK to Visual Studio
ColleagueSDK for .NET allows you to add DataContract and Transactions from Colleague to your VS projects. You will need this if you want to compile/customize Ellucian Self Service. In this post I will use ColleagueSDK for .NET version 1.8 and MS 2013.
First, you can download the installer from SA Valet.
Run the .exe file and you will have this folder created.
Run ColleagueDataContractGenerator.vsix and the VS extension will be added to your local Microsoft Visual Studio. ColleagueSDK no longer supports VS 2010 and only supports 2012 and 2013 so far. Make sure you have one of those installed first.
To add Colleague parameters, double click on CollSDKParamsEditor.exe. You will see the editor as following:
Click on Help/View Help if you need help filling out the screen. This form requires similar information you use to login to Colleague Studio. Once you're done, hit File/Save to save your configuration file that you can then use in your VS project.
After the extension has been added to VS, you should be able to add DataContract or Colleague Transaction to your VS project.
First, you can download the installer from SA Valet.
Run the .exe file and you will have this folder created.
Run ColleagueDataContractGenerator.vsix and the VS extension will be added to your local Microsoft Visual Studio. ColleagueSDK no longer supports VS 2010 and only supports 2012 and 2013 so far. Make sure you have one of those installed first.
To add Colleague parameters, double click on CollSDKParamsEditor.exe. You will see the editor as following:
Click on Help/View Help if you need help filling out the screen. This form requires similar information you use to login to Colleague Studio. Once you're done, hit File/Save to save your configuration file that you can then use in your VS project.
After the extension has been added to VS, you should be able to add DataContract or Colleague Transaction to your VS project.
Subscribe to:
Posts (Atom)