Idea
Update Authentication Profile through REST API
Our Containerized Pega is deployed on Azure Cloud and we use Azure Storage as repository for storing documents that are generated as part of Pega cases. In order to connect to Azure Storage, we have created a Azure Repo rule and an authentication profile rule (with Azure Storage Account Credentials). As per our Cloud Security Policy, the Azure Storage keys should be periodically rotated (once in 90 days). At present, we have 15 Pega environments (the number will increase in future) and updating the Authentication Profile rule whenever Storage Key changed is a laborious work. We want Pega to support REST API for updating Authentication Profile.
Please consider this as an enhancement request and do let us know when the feature will be available
No Suman. We didn't create any REST service in our application. We wanted this feature OOTB.
Ok. You might want to think of developing a service REST and consume the new REST service in Pega to update the Repository key in the rule form instead of updating the all the environments manually.
--Suman
I agree but we don't want to maintain the overhead of updating the service in the scenarios where Pega changes its internal code and the service fails because of the Pega's update.
Agreed. But you can give it a try and retest your code when ever Pega version is upgraded.
Thanks,
Suman
At this time we have no plans to add this functionality to a future release of Pega Infinity. We will consider this for a future release, but can give no commitment at this time.
Thanks for the response Marty.
Is it not possible to create a feedback item for the enhancement and share the ID with us?
Hi CharanTejaS1426 ,
Thank you for sharing your idea here in the Pega Collaboration Center (PCC)!
I have submitted this idea on your behalf in our internal system for feature enhancements and updated your post with the associated FDBK-ID. You can take this ID to your Account Executive for next steps.
Thanks and keep the ideas coming!
Kayla Metivier | Moderator | Pega Collaboration Center
Did you face any issue by creating your own service REST , which updates the authentication profile with the new storage keys instead of manually updating every Pega instance?
Thanks,
Suman