sso connection

Answered

Comments

20 comments

  • Avatar
    Ichiro

    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.

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    yes, I know, we're using it now.  (ldap)
    But the SamAccouname field is used by network optix

    But I would like to use the User Principal Name (UPN) field instead of SamAccouname
    The SamAccouname field is Pre-Windows 2000)., ( the old way)

    https://morgantechspace.com/2014/04/samaccountname-vs-userprincipalname.html#:~:text=The%20samAccountName%20is%20the%20User,Windows%202000%20and%20later%20versions.

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    did you have any update ?

    0
    Comment actions Permalink
  • Avatar
    Ichiro

    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.

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    Can you tell me when It’s  supported? 

    Can I customize this myself somewhere in the software installation 

    0
    Comment actions Permalink
  • Avatar
    Ichiro

    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.

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    The problem is that our users log on to all our software with UPN.
    Then they use the email address, with sammacount this is not possible .

    Then the users have to use a different login and that is confusing

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    Do you understand my problem?

     

    Is there a solution?

    0
    Comment actions Permalink
  • Avatar
    Ichiro

    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.

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    thanks for your feedback

    0
    Comment actions Permalink
  • Avatar
    Luke Shaw

    Also keen to see SSO with Azure AD. How can we escalate this and get priority on this?

    1
    Comment actions Permalink
  • Avatar
    Veronika Nazarova

    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. 

    0
    Comment actions Permalink
  • Avatar
    Luke Shaw

    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.

    2
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    Hi

    Is there any news yet?

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    Now version 5 has been launched in the meantime.

    What about the SSO function of Azure AD SSO?

    0
    Comment actions Permalink
  • Avatar
    mathijs brugmans

    We are also very interested in Azure AD SSO. 
    Is this in the roadmap in the near future?

    0
    Comment actions Permalink
  • Avatar
    Iwan Bourgonje

    Hi

    Is there any news yet?

    0
    Comment actions Permalink
  • Avatar
    ralph.helmuth

    Any update on this? SSO integration would be a huge benefit for us. 

     

    0
    Comment actions Permalink
  • Avatar
    Rick Akkermans

    Hi, 

    Any news about the MS Entra ID SSO intergration? we have a project where this is required

    0
    Comment actions Permalink
  • Avatar
    Bert Proesmans

    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.

    0
    Comment actions Permalink

Please sign in to leave a comment.