Forum Discussion

justinhaynes's avatar
justinhaynes
New Contributor
2 months ago

How do I transitioning from 1:1 mapping of authentication to authorization to simpler options?

I have never taken the following suggestion:

In this example, let's say I work for Consult-o-rama, and the account referred to is Microsoft here is a login called Consult-o-Rama in my Consult-o-Rama vault dedicated to all things Consult-o-Rama. (I'm an employee of Consult-o-rama)

the Sharepoint referred to here, then, is a SharePoint of a  company which was a joint venture 30 years ago and with whom we have a close relationship. They have their own AD, but federatio nis such that we are allowed to log into their sites separately using our same login. Likewise we can switch orgs in Teams and use their separate teams with the same credentials.

Sites appear in this login record in 1Password so that this credential can autopopulate on any sites i've put into the sites fields there. 

Other background:

  • I have 4+ vaults.  consult-o-rama, client 1, Client 2, Persional, and then Client <#> for however many clients I need to have them for.  
  • I use separate browser identities and have the vaults in the plugin filtering only on the relevant vaults.
  • the login credential record "Consult-o-Rama' is one of 5-10 microsoft account.  I log into at least that many SharePoints
  • None of my login credential records are named Microsoft or SharePoint.

 

How can I best use the funtcionality I'm being prompted to use without:

  • Creating duplicate records of login credentials.
  • Being clear about mapping identities an being able ot lble "Microsoft" in this example instead as "Consult o Rama', and "SharePoint" instead as "consult-o-rama" SharePoint.  So that in the future I can map  1 to many and many to 1 logically and without confusion?

 

Thanks!,

No RepliesBe the first to reply