Deploying an Authentication Service
Is it possible to deploy an authentication service rule to higher environments by parameterizing the hostname and password?
Accepted Solution
Updated: 23 Sep 2022 17:10 EDT
Pegasystems Inc.
GB
@Bahri ,
Authentication Services are Data (Data-Admin-AuthService) and can be modified in all environments without unlocking the associated ruleset.
You could do as @PriyankarG suggests and provide a Data Page with an Application Setting. However, in most cases you need to adapt and configure the Authentication Service to the specific values per environment with other values (Binding, Certificates, etc) or even as happens with the SAML Authentication Service you'll need to setup the IdP to recognise the new environment as SP so I can see a big advantage in parametrising a data form that would likely need to be adapted anyway.
This doesn't mean that you don't use migrate the general settings and configuration like Mapping or Activities settings that will be consistent through environments. It simply means that it is likely you'll need to do more than just adjusting the URLs.
Knowledge Expert
NL
Hi,
You can do the deployment of Authentication service rule by association rulest with that rule. You can't parameterized the host name but you can refere the host via Global Resource Setting.
For e.g.: =D_Env.hostName.
You can construct a datapage to populate the host name based in the production level
Türkiye IS Bankasi
TR
Thank you for your response ,
Is it possible to do the same thing for the password somehow?
Accepted Solution
Updated: 23 Sep 2022 17:10 EDT
Pegasystems Inc.
GB
@Bahri ,
Authentication Services are Data (Data-Admin-AuthService) and can be modified in all environments without unlocking the associated ruleset.
You could do as @PriyankarG suggests and provide a Data Page with an Application Setting. However, in most cases you need to adapt and configure the Authentication Service to the specific values per environment with other values (Binding, Certificates, etc) or even as happens with the SAML Authentication Service you'll need to setup the IdP to recognise the new environment as SP so I can see a big advantage in parametrising a data form that would likely need to be adapted anyway.
This doesn't mean that you don't use migrate the general settings and configuration like Mapping or Activities settings that will be consistent through environments. It simply means that it is likely you'll need to do more than just adjusting the URLs.
Ernst & Young LLP
MT
You have not mentioned the auth service type in use. But, you check the fields listed on this article that supports Global Resource syntax which is one way of avoiding static config values.