Configure SSO between Azure AD and Samsung Knox

Published On: June 9, 2022Last Updated: January 10, 2024By Tags: , 2 min readViews: 695

Configuring SSO in Knox

  • Login to Samsung Knox
  • In the top-right hand corner, click your Avatar icon, then select Account Information
  • On the left-hand side click SSO Settings
  • Browse to the Azure Active Directory Portal
  • In the left-hand pane, click Azure Active Directory, then click Enterprise Applications
  • Click New Application
  • Enter Samsung Knox and Business Services into the search box
samsungsearchsso
samsungsearchsso
  • Click the app, then click Create
  • Once created, click Users and group
  • Click Add user/group, then click None Selected under Users and Groups to add your assignment.
Note

I recommend using a dedicated Azure AD group for Samsung Knox Administrators

samlconfig
samlconfig
  • Navigate back to the SSO Settings page in Samsung Knox
  • Paste the copied contents into the App federation metadata URL box
samsungssosettings
samsungssosettings
  • Click Connect to SSO
  • Sign in with your AAD Credential
Warning

The user you initially configure SSO with must be the Super Admin Account. Ensure the user was selected or is within a selected group in steps 10/11.

Things to be aware of

  • If your account already has permissions to another Knox Suite, you will not be able to use your account
  • Once you configure SSO for Knox, you can not use a mixture of Samsung and SSO Accounts, you can only use SSO Accounts.
  • The App on the My Apps will not sign you into Knox
  • Any account that has already been configured will continue to work with their SSO Credentials providing they are in scope of enterprise app
  • To add a user to Knox, you are still required to send the invite in the first instance from Knox, Adding them to the scope does not suffice
  • If when you sign-in you receive a Sorry, you don’t have access screen, ensure that a Samsung Knox administrator within your organization has configured an account for you.

Conclusion

Using SSO for applications such as Knox will save admins time and effort storing multiple password and identities.

I tried numerous ways to configure the application to open the Knox portal from the MyApps page to no avail. If you have managed to succeed in doing so, I would love to hear from you :).

Configure SSO between Azure AD and Samsung Knox

Published On: June 9, 2022Last Updated: January 10, 2024By Tags: , 2 min readViews: 695

Configuring SSO in Knox

  • Login to Samsung Knox
  • In the top-right hand corner, click your Avatar icon, then select Account Information
  • On the left-hand side click SSO Settings
  • Browse to the Azure Active Directory Portal
  • In the left-hand pane, click Azure Active Directory, then click Enterprise Applications
  • Click New Application
  • Enter Samsung Knox and Business Services into the search box
samsungsearchsso
samsungsearchsso
  • Click the app, then click Create
  • Once created, click Users and group
  • Click Add user/group, then click None Selected under Users and Groups to add your assignment.
Note

I recommend using a dedicated Azure AD group for Samsung Knox Administrators

samlconfig
samlconfig
  • Navigate back to the SSO Settings page in Samsung Knox
  • Paste the copied contents into the App federation metadata URL box
samsungssosettings
samsungssosettings
  • Click Connect to SSO
  • Sign in with your AAD Credential
Warning

The user you initially configure SSO with must be the Super Admin Account. Ensure the user was selected or is within a selected group in steps 10/11.

Things to be aware of

  • If your account already has permissions to another Knox Suite, you will not be able to use your account
  • Once you configure SSO for Knox, you can not use a mixture of Samsung and SSO Accounts, you can only use SSO Accounts.
  • The App on the My Apps will not sign you into Knox
  • Any account that has already been configured will continue to work with their SSO Credentials providing they are in scope of enterprise app
  • To add a user to Knox, you are still required to send the invite in the first instance from Knox, Adding them to the scope does not suffice
  • If when you sign-in you receive a Sorry, you don’t have access screen, ensure that a Samsung Knox administrator within your organization has configured an account for you.

Conclusion

Using SSO for applications such as Knox will save admins time and effort storing multiple password and identities.

I tried numerous ways to configure the application to open the Knox portal from the MyApps page to no avail. If you have managed to succeed in doing so, I would love to hear from you :).