Page History
...
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||
This service connects to Yellowfin and retrieves a login token for a given user. The user is specified using a user ID (such as an email address or another type of ID depending on the Login ID method). When this token is passed with the Yellowfin Login URL, it will disable the login screen for the authenticated users and their session will start immediately. For example, if admin@yellowfin.com.au is a web service admin user, then the following request for this call could be made.
Redirecting to Yellowfin with the Login TokenUsing the token received from the web service call (the contents of AdministrationResponse.LoginSessionId), you can forward the user to the URL:
This URL will bypass the authentication screen in Yellowfin and take the user directly into Yellowfin.
Using the token with the JavaScript APIThe SSO token can also be used with embedded JavaScript API widgets. The token is added to the scriptlet URL like this:
Complete ExampleYou can use the following LOGINUSER example. To try it out, follow these steps;:
|
...
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This service is a drop in replacement for LOGINUSER, but the password for the user being logged in is not required. The user can log in using only their user nameusername. An extra parameter needs to be added to the Configuration table of the Yellowfin database to enable this functionality:
You will receive a web service error 26: UNSECURE_LOGIN_NOT_ENABLED if this configuration option is not added to the Yellowfin database.
|
...