Open michael-allen-deloitte opened 1 year ago
Thanks @michael-allen-deloitte , PM is saying this is a good enhancement/candidate for our 4.1 release target. Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-601950
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days
Is there a target release date for this feature? Our team could really use this to maintain sign-in page code in our pipeline. I saw the comment above saying it was a good candidate for v4.1. Is it still planned for v4.x release?
@huy-keydata there is not, however we aimed to tackle this before year end
Any progress @monde or @duytiennguyen-okta 😉
Community Note
Description
Add support for the new multi-branding API outlined in this documentation: https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Customization/
Specifically the new API calls that allow for managment of the code on custom sign-in/error pages, for example:
https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Customization/#tag/Customization/operation/replaceCustomizedSignInPage
New or Affected Resource(s)