OKTA Intergration for Authentication
New
Hello team,
We have OKTA integration for Authentication here and were wondering if something we can use to integrate into NX Witness ?
is it was asked users ago but unsure if it's changed as a result of the 2FA integration some months past.
Many thanks for the support
regards
David
Glad that NX is working on this. This functionality sounds great, but please build in SAML support so we can use our own identity provider. TOTP is better than nothing, but the industry standard is SAML support now. This would allow us to use Duo for providing MFA and would fit in with our SSO standards.
This is convenient from a user/admin perspective, but it also GREATLY increases security as we can have contextual policies we can configure within Duo (or JumpCloud, Okta, MS AAD / M365). Examples of that would be limited access to a specific device, an authorized network, blocking mobile access, etc... A lot of added functionality, but all dependent on SAML for MFA.
I think TOTP is needed as a minimum, but to scale, SAML is required as well.
-
It appears that you're inquiring about integrating OKTA authentication and SAML support with NX Witness for enhanced security and user management capabilities. Integrating OKTA or other identity providers via SAML (Security Assertion Markup Language) can indeed enhance security and streamline user authentication.
However, to achieve official website this integration, it would require development and configuration work from both the NX Witness and OKTA sides. Here are the general steps to achieve such integration:
NX Witness needs to have SAML authentication support built-in or added through custom development.
The NX Witness system administrator would configure the SAML settings within NX Witness. This includes specifying the identity provider (OKTA), SAML endpoints, and certificates.In the OKTA admin console, you would configure the NX Witness application as a service provider, setting up the SAML connection.
You would define the SAML attributes and user attributes mappings so that OKTA can provide user information to NX Witness.Once configured, you should perform testing to ensure that SAML-based authentication is working correctly.
This would involve users logging in to NX Witness through OKTA, and NX Witness accepting SAML assertions for authentication.If you require multi-factor authentication (MFA) through OKTA, you would configure this within OKTA itself. OKTA provides various MFA options, including TOTP and push notifications.
With SAML integration, you can enforce security policies and access control rules within OKTA, ensuring that only authorized users gain access to NX Witness.
Regularly review and update the SAML integration as needed to accommodate changes or updates to OKTA or NX Witness.
Please note that specific configuration steps and requirements may vary depending on the software versions and capabilities of NX Witness and OKTA. It's essential to consult the documentation and support resources for both systems and consider engaging with the technical support or development teams of the respective products to ensure a successful integration.
Additionally, check if NX Witness has added or plans to add SAML support in recent updates, as this information may have evolved since your inquiry.
Please sign in to leave a comment.
Comments
2 comments