In the learning module of Acces management it is mentioned that
"All users need an account in eramba even if they authenticate using an external service. "
Also in the learning video of “Introduction to SAML Authenticator” the presenter creates a user account in eramba as well. and just uses Azure SAML for authentication and redirection.
So in our company we are using OKTA SAML authentication. Just as confirmation, I cannot use any SAML provider as an Identity Provider right? Ill need to create their account in eramba as well?
Like eramba cannot pick up my user ID and password from OKTA so that i do not have to go and create account for all employees in the eramba as well.
You can interface with Okta via LDAP and you can auto provision/deprivation users based on group membership within eramba. The downside here is that you lose the one click SAML login button, so users will just have to use their username and password. I believe you can still do MFA with Okta in this scenario, but I haven’t tested it (or… this idea at all).
(Ninja edit… I wonder… If both can be used at the same time actually… LDAP group sync but SAML as the authenticator).
im often scared when i see people creating many accounts in eramba…%99 of the times you only need 2 x number of departments in the scope of your GRC program.
if your company has 10 department, that is 20 accounts.
Well, if you publish all your company policies on Eramba’s policy portal, you could well want all your staff to log in there (particularly if certain policies are only for the eyes of certain staff)
If I have all my policies are in Eramba then ill need to give access to all employees in the org. that would be like 800+ users. so would need to create accounts for them all in Eramba it seems.
plus then. our policy review cycle is also cross-functional.
Seems like i can use LDAP sync. but that’s about it.
We have all of our policies and other security related documents in Eramba for managing them and assign various people who are responsible for owning and reviewing them, obviously these need access. Along with this we allow all our employees to view the documents on the policy portal, but with access controlled by the LDAP groups as we don’t want to make it public with no authentication. This makes great use of the Policy Portal, unless I have it wrong and it’s for another use!
We use LDAP to automate our accounts and use groups, we don’t use or create local accounts except for the Online Assessments module where external users will need to login to complete the assessment.