GetAutoLoginLink | |
---|---|
Definiton | Allows the application to redirect its user to a GEODI interface without requiring a login screen. Links obtained via this service do not requiere a login page. The user specified by the trusted application is considered to be logged in to the system. Only applications defined underSettings/ClientToken can make use of this service. Application is validated by making a request to ValidateURL in the definion. If a .net soap api that takes same parameters and returns same object as an output is implemented, then |
Request | [GEODIURL]/TokenHandler?op=GetAutoLoginLink&ClientID=[ClientID]&ClientValidator=[ClientValidator]&LoginUser=[LoginUser]&UserSession=[Token]
|
Workflow | |
Example GEODI settings file | A UTF8 encoding definition such as the following should be saved in a jSettings file and dumped in the Settings/ClientToken folder that the GEODI application can reach. { ClientID:"MyClientID", } ClientValidator is passed between request headers, even if {ClientValidator} is used in ValidateURL content. If a GEODIRequestHeader definition is made, this information is added to the ValidateURL request as a header. It can be used to verify that the calling application is GEODI. |
HttpMethod | GET, POST |
Expected Errors | 401 Unauthorized access / Access denied 403 Forbidden 511 Network Authentication Required 452 ClientValidator could not be verified 453 LoginUser required 454 Invalid Client Id or empty ValidateUrl 455 LDAP domain not found (This error can only be received when trying to find the LDAP domain when username is passed as LDAP: username) 500 -Other errors, Web Request errors- |
Expected Result | Returns the URL containing the Token information. |
Example applications |
GetAutoLoginToken | |
---|---|
Definition | Same with GetAutoLoginLink . Returns only Token, not URL+Token. |