The sign-in page typically collects the user's credentials through an HTML form submit or POST and validates the credentials against your Okta org by calling the Authentication API to obtain a session token. This scenario is ideal for deployment scenarios where you have a custom sign-in page but immediately want to launch an Okta app after a user signs in without returning to a landing page. HTTP/1.1 302 Moved Temporarily Set-Cookie : sid=000aC_z7AZKTpSqtHFc0Ak6Vg Path=/ Location : Retrieve a session cookie by visiting an application embed link This example shows how the location is returned in the redirect response. For more information about the character limitation, see the Microsoft documentation (opens new window). If the redirectUrl is only going to Okta and the request parameters are longer, then use a POST request to this API and provide additional request parameters as POST form parameters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |