The Controller Configuration entity is how you can configure a stock controller to have some different behavior for your instance of services. This largely involves:
- Changing the authorization plugin
- Changing the caching policy
- Allowing anonymous access to the controller
You should never modify a stock controller configuration record. These stock records are used for Aptify's family of products and your changes may be overridden when you take maintenance. Instead you should create a record specific to your applications needs and add it to your service application.
As an example, lets say you want to allow anonymous access to the Space Threads controller for your service application. There is currently only one Controller Configuration record for the Space Threads controller. Here is its definition:
If you change this record to allow anonymous access, you will be allowing anonymous access to any other service applications using this configuration record. This is never what you want to do. Instead, you should create a new record and configure the controller according to your application's needs.
- Name - An informational identifier to refer to this record as.
- Controller - The controller for this configuration uses.
- Authorization Plugin - The plugin that is called before controller execution to determine if the user should be allowed to call this controller. Some end points have a stock Authorization Plugin that enforces metadata constraints like the records in Service Application Entities.
- Caching Policy - The client side header caching policy.
- Enabled - This field does not do anything.
- Require Authentication - Check this to call end point without a valid token.
- Allow Anonymous - Check this to allow end point call without a valid token. This requires that you to define an Authorization Plugin for this record.