![]() ) should be improved definitely and support can be improved. The only bad things to mention are that possibilities for session management (get overview of users with current valid tokens with information regarding applications, invalidate given tokens. Furthermore the SLA goal of 99,99% availability now makes it fit for business critical applications too (since the SLA changed to 99,99% we did not experience any big issue). On the other side, as we are also leveraging O365 services, we need AAD in any case, therefore to reduce complexity in the whole authentication architecture we decided to consolidate IdPs and MFA providers and have no federation in place anymore. It provides definitely the most advanced strong user authentication methods in combination with Windows 10 (passwordless - WHfB, FIDO2, Authenticator sign-in) to create a real password-less authentication journey for our users. We decided to go with AAD as our central Identity Provider for Workforce IAM and are quite satisfied up to now. We use multiple platforms on a daily basis to work with our clients and keep our business running smoothly and Okta SSO provides us with a single point of access with a single password to all integrated applications and platforms to free us from the annoying long login process. Okta not only provides our users with simple and quick access to our applications but also allows us to stay free and unstressed from its maintenance concerns. I switched to this from Microsoft Azure Active Directory to Okta SSO because it was hard to administer and maintain. Okta not only has improved our corporate Security but also allows us to keep our users and employees happier as well as IT staff at rest with this best-in-class SSO solution. Okta Single Sign-on has proved the most powerful weapon for us at that time that has streamlined the process on both sides, providing our users and staff with a single point of entry and self-service rest opportunities. During the pandemic situation of Covid-19, our end users weren't the only ones who had to juggle various login credentials but our IT staff was also hampered by the number of time-consuming password resets that must be handled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |