sso connection
Answered
How can I connect with sso to our network?
We want to link the users from ms Active directory / azure /office 365
I now use the ldap option, but that's where the sAMAcointName is used instead of the UserPrincipalName
Is it possible to use the UserPrincipalName ? Can I change the field settings ?
-
Thanks for reply. We use the product in a local government context, and all our users are identified using Azure AD SSO. We want cloud and client access to use this authentication and identity. That way when a user is disabled in Azure AD, all connected systems are also disabled for that user. I would be more than willing to discuss this further, if required. It’s currently one of the most lacking features of an otherwise awesome product.
-
Hi Iwan Bourgonje ,
Nx Witness now integrates with an OpenLDAP or Active Directory system. You would be able to configure the LDAP server and allow the users to login the Nx Witness with the same account. Here is the article for LDAP function.
So far, Azure / Office 365 is not yet supported, and unfortunately, it is not yet put in the near future roadmap.If you do have some requests and some projects that need this kind of big integration, it is suggested you can talk to the local distributor and they would be able to help you to raise the requests with our sales input.
Thanks for your feedback.
-
yes, I know, we're using it now. (ldap)
But the SamAccouname field is used by network optixBut I would like to use the User Principal Name (UPN) field instead of SamAccouname
The SamAccouname field is Pre-Windows 2000)., ( the old way) -
Hi Iwan Bourgonje,
Thanks for the feedback.
SamAccouname field is used as the recommendation at the moment.User Principal Name (UPN) so far has not yet fully supported.
Thanks. -
Hi Iwan Bourgonje,
So far, we don't have the ETA at the moment. It was not yet in the roadmap. However, I put in the internal wishlist now.
Unfortunately, you might not be able to customized it.
Please use the SamAccouname field at the moment.Thanks.
-
Hi Iwan Bourgonje ,
We fully understand your questions and knows the request detail very well and clearly.
Unfortunately, so far, we don't have the plan to update the LDAP function for supporting UPN. This is a good feedback, soI have put this in the internal wishlist, however, I am afraid this is not implemented in a short period of time.Regarding to the question you raised:
1. You can't customize it. We don't provide the configuration or customization for the users. So please use the SamAccouname field at the moment.
2. So far, we support SamAccouname, and this is the possible option at the moment.
Please use the SamAccouname field at the moment if you would like to use LDAP for Nx Witness.Thanks.
-
Hi Luke,
This feature is already on our roadmap with one of the highest priorities. In the upcoming release we've done a lot of refactoring to prepare our infrastructure for SSO implementation. It took quite a while as all the authentication is on the core of our software.
What would really help is if you share more details on how you see SSO integration in our software.
-
I'd like to use the OpenID authorization flow. For the purpose of delegated authentication through our Azure user database. User pre-provisioning on the server is a nice-to-have but not a blocker for us.
The most basic and straightforward implementation would be using the networkoptix cloud and an authorization code flow. The networkoptix cloud website brokers between the Azure user database and Networkoptix cloud users.
Admins should be able to pre-provision cloud accounts on their servers with user principal names from their domain, and the networkoptix website links cloud logins to cloud accounts based on user principal name.
Please sign in to leave a comment.
Comments
25 comments