Major hassle with Azure AD implementation

En1
En1
Community Member
edited August 2023 in SCIM Bridge

Several problems:

1) SCIM bridge. I understand you don't want to have the keys yada-yada, but there must be a way to separate users and groups out so that one can use the safest mechanisms in Azure AD to sync only these into the 1Password tenant without being a Kubernetes engineer with an own SCIM bridge just for 1Password. I've set up hundreds of apps where the integration is simple.

2) Azure AD sso provides ease of login as well as the latest security. Not only is the App setup itself the first time I see this kind of setup implemented, but you exclude owners from it. This means the owner - the most sensitive user - is left out of the heavy security machinery that is Azure AD. Why?

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Comments

  • En1
    En1
    Community Member

    3) Lack of link to the SSO/SCIM setup when you are in the Wizard. Linking to a Microsoft article isn't enough for a professional company.

  • En1
    En1
    Community Member
    edited August 2023

    Where is the post delete button

This discussion has been closed.