P
Peter Judge
Guest
I'm using what's currently there in the CP: username and domain and domain translates into a company. So in order to change the company (without needing to re-authenticate the user) I was hoping to replace the CP (which is managed and stored by the sping/rest manager stuff) with a CP with the new values. May it be the ability to replace the CP or have additional attributes that spring or the rest manager store for us? The CP has no idea about a company: it knows domains and tenants and roles and properties. Currently you can dynamically set roles (from the auth provider/realm). Soon you will be able to dynamically set properties from a realm (which may help or solve your problem) before the CP is sealed. Would that meet your need? The user would not change domains, but as part of login, you would set the "LoginCompany" property appropriately before the CP is sealed. So going with the session-id from the CP and storing the actual login company in a session context DB table might be a quick fix then until that enhancement might be implemented? It would.
Continue reading...
Continue reading...