Changes between Version 39 and Version 40 of S3/S3AAA/OrgAuth


Ignore:
Timestamp:
09/04/12 11:09:01 (9 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3/S3AAA/OrgAuth

    v39 v40  
    8080
    8181  '''NOTE:''' The "Default Realm" setting can be dangerous and may be inappropriate for most multi-tenancy settings, because the user would automatically receive this role for any entity they will ever join in future - without that entity being anyhow in control of this. However, in certain deployments, this dynamic realm may still be convenient practice.
     82
     83To check which realms a role of the current user applies for, you can access:
     84
     85{{{
     86    realms = current.auth.user.realms[role]
     87}}}
    8288=== Realm Hierarchy ===
    8389