When creating inline hooks in the Admin Console (or by API), administrators or developers can now select OAuth 2.0 authentication and choose between two methods of OAuth 2.0: Client Secret or Private Key. Tokens ensure secure calls to external web services. To improve the security of inline hooks, Okta now supports authentication with OAuth 2.0 access tokens. Although sent with SSL, the header or custom header authentication didn’t meet more stringent security requirements for various clients and industries. Okta inline hook calls to third-party external web services previously provided only header-based authentication for security. OAuth 2.0 authentication for inline hooks
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |