Hi Peplink,
To enable companies to centrally manage theire users, it should be possible in a modern environment to bind the peplink-ID of a company domain against its own iDP like AAD or Okta by using SAMLv2 and do provisioning with SCIM.
This is super default for a security product in 2023.
Best regards
Linus
I second this request.
For Peplink ID this is already possible. We have linked AAD to Peplink ID and I can login to inControl with my Microsoft business account.
Donāt remember which steps to take, but it is already possible.
Hi @padaco-daniel ,
Right, there is a button ālogin with M365ā that enables you to forward authentication to MS. Never the less, you can not restrict access method to that and it is always possible for users to fall back to username & password. So this is not a valid solution if you want to increase security and deploy centralised iDP as default authentication.
Best regards
Linus
All systems I have linked to M365 SSO have the same that ālocal usersā still work after linking to AAD. In other systems I have just removed the ālocal usersā from the systems and only the AAD entries are left. Just kept 1-2 fail save accounts in case AAD/SSO would be down someday.
Havenāt tested what inControl does when you remove a local user from inControl if the account can still login when given the proper rights inside the Enterprise Application in AAD.
I need BYO IdP before I can implement InControl for my enterprise. Cradelpoint Netcloud does this today (7/29/2024) which will be direction I have to go until this is corrected.