How Does Authorize Work?

Attribute Certificate Servers (ACS) and Agents drop the certificates they may be holding in their caches when they receive Invalidation Events for them.

1. Broker submits an authorisation request to an Agent.
2. Agent looks up a certificate locally for the authorisation request it receives.
3. Agent requests a certificate from an Attribute Certificate Server (ACS).
4. The ACS looks up the certificate locally.
5. The ACS asks the Repository to generate a new Authorisation Attribute Certificate.
6. The Repository generates a new certificate.
7. It then returns it to the ACS.
8. The ACS caches the returned certificate.
9. It then returns it to the requesting Agent.
10. The Agent caches the returned certificate.
11. The Agent processes the request, and sends the response back to the Broker.
12. Administrators edit the Repository.
13. Invalidation event(s) are sent.
14. ACSs and Agents drop certificates held in their cache when they become invalid.