Example

User Ronan Rooney attempts to register a Person. He enters the registration information on a client screen and clicks a button. The client application attempts to call the Person.register method. The server application successfully authorizes that Ronan Rooney is permitted to access the Person.register method. The data to support this authorization is as follows:

• User Ronan Rooney has been assigned the Security Role 'Case worker';
• The Security Role 'Case worker' is a member of the Security Group 'Front office';
• The Security Group 'Front office' has been granted access to the Security Identifier 'Person.register'; and
• The Security Identifier 'Person.register' relates to the Function Identifier 'Person.register'. This relationship is stored as a Security Function Identifier/Security Identifier which links this Security Identifier and Function Identifier.

Technical Notes

• Each Function Identifier will have exactly one Security Function Identifier/Security Identifier; and
• Each Security Identifier may have at most one Security Function Identifier/Security Identifier

...thus each Function Identifier will have exactly one Security Identifier and each Security Identifier may have at most one Function Identifier.

For more information see the Cúram Application Administration Guide.