ALTER AUTHORIZATIONPROFILE
Alters or enables an authorization profile in a specified deployment. If a non-localCredentialStore profile is enabled, a communication and configuration test is triggered. If the test passes, the profile is set, otherwise no change occurs. You need to restart your Microservices deployment, before this profile gets loaded. Service Manager automatically loads the profile.
The localCredentialStore profile can be set, but its content cannot be changed.
Syntax
ALTER AUTHORIZATIONPROFILE *profile-name*
DEPLOYMENT *deployment-name*
( [ ENABLE ]
[ ID *client-id* [ SECRET *client-secret* ] ]
[ DISCOVERYURI *tenant-discovery-uri* ]
[ GROUPS
( SECURITY *security-group*
| [ ADMINISTRATOR *administrator-group* ]
| [ OPERATOR *operator-group* ]
| [ USER *user-group* ]
) ]
[ TTLSECONDS *ttl-number* ]
[ DESCRIPTION *description* ]
)
ENABLE
Use this option to enable the profile.
The other options used in this command are the same as the [ADD AUTHORIZATIONPROFILE](add-authorizationprofile.html#GUID-EB12DF21-6A0B-40C8-9032-3E5BB832AB44) command.
Example
The following example shows how to enable a profile using this command:
ALTER AUTHORIZATIONPROFILE apn DEPLOYMENT ServiceManager ENABLE
The following example shows how to clean the administrator group name.
ALTER AUTHORIZATIONPROFILE apn DEPLOYMENT ServiceManager GROUPS ADMINISTRATOR ''
The following example shows how to update the client ID and secret.
ALTER AUTHORIZATIONPROFILE apn DEPLOYMENT ServiceManager
CLIENT ID 1234567890abcdefghijklmnopqrstuv SECRET 12345678-90ab-cdef-ghij-klmnopqrstuv