![]() ![]() See the sessionFlags description for details. The sessionFlags is used to indicate the different options for the session. The user has whatever the privilege an anonymous account is set in the Data Source.Īnonymous authentication mode does not require a user name and a password when CreateSession is called. When AuthMode is set to "DssXmlAuthAnonymous", MicroStrategy Server will log the user in as an anonymousĪccount. The Web Server platform is not necessarily Windows NT, and as such this cannot be a valid option from the Java WebAPI. The setting for authMode of DssXmlAuthNTCredential is disabled for the Java-based Web API. When authMode mode is DssXmlAuthStandard, uid/passwd parameters are required. This ID can be used by MicroStrategy Server for monitoring purposes. When using the default, a hard coded "Web Server" is used. The user who uses the machine are examples of clientID. Client machine names, IP addresses or the names of The clientID parameter is used for client identification. If the sessionFlags is set to anything else and a new password is provided, the To change the password, the sessionFlags has to beĭssXmlSessionChangePwdOnCreate. With CreateSession, a user can change the password. The user cannot perform any project-related operations, like submit reports or documents, or ![]() The user can only check inbox messages and This session, the user can only perform project independent operations. If projectName is empty, the session is created at the Intelligence Server without connecting to any project. ![]() By creating a session, a user is authenticated in the Server to perform the operations that are allowed for its account. Almost all operations (except GetProjects and CheckVersion) of the Web API require a session ID. Which is structured as follows, where the individual locale IDs must beĬreates a session in the Intelligence Server. If an invalid sessionToken is provided, a 401 Unauthorized status code is returned.CreateSession(String, String, String, String, int, String, int, int)īy replacing the single locale parameter with a regional options XML, The response contains the new Session for the user if the sessionToken is valid. The session token obtained through the Authentication API Note: This operation can be performed anonymously without an API token. Retrieving a session cookie by visiting an application embed link.Retrieving a session cookie by visiting a session redirect link.Retrieving a session cookie by visiting the OpenID Connect Authorization Endpoint.Instead, use one of the following flows to obtain a SSO session with a sessionToken: Use this API if, for example, you want to set the session cookie yourself instead of allowing Okta to set it, or you want to hold the Session ID to delete a Session through the API instead of visiting the logout URL.ĭon't use this API unless you need a Session id. Get startedĮxplore the Sessions API: (opens new window) Session operations Create Session with a session tokenĬreates a new Session for a user with a valid session token. A session token for a user is equivalent to having the user's actual credentials. Note: Session tokens are secrets and should be protected at rest and during transit. Retrieve a session cookie by visiting an application embed link.Retrieve a session cookie by visiting a session redirect link.Retrieve a session cookie by visiting the OpenID Connect Authorization Endpoint.A session token is returned after successful authentication, which can be later exchanged for a session cookie that uses one of the following flows: Okta provides a very rich Authentication API to validate a user's primary credentials and secondary MFA factor. Session tokens can only be used once to establish a Session for a user and are revoked when the token expires. Session tokenĪ session token is a one-time bearer token that provides proof of authentication and may be redeemed for an interactive SSO session in Okta in a user agent. A session cookie has an expiration configurable by an administrator for the organization and is valid until the cookie expires or the user closes the Session (logout) or browser application. Okta uses an HTTP session cookie to provide access to your Okta organization and applications across web requests for an interactive user agent such as a web browser. Direct authentication is supported through the Authentication API or through OIDC using the Resource Owner Password flow. Note: The Sessions API doesn't support direct authentication. See FAQ: How Blocked Third Party Cookies Can Potentially Impact Your Okta Environment (opens new window). Note: Some browsers block third-party cookies by default, which disrupts Okta functionality in certain flows. The Okta Sessions API provides operations to create and manage authentication Sessions for users in your Okta organization. Okta uses a cookie-based authentication mechanism to maintain a user's authentication Session across web requests.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |