Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Deploying an Application with Subscribed Authorization Scheme's - 21.2.3

Joe RFeb 17 2022

Version 21.2.3
Hello,
Here's the scenario, I have multiple applications that are part of an overall application that are connected by SSO.
The "main" application contains the Navigation and Security settings. We've created the Roles in the Application Access Control and the Authorization Schemes in the "main" application. Then in the other applications we've created copies of those Authorization Schemes that are to be used in the other Application and Subscribed to the Authorization Scheme in the main application.
The idea was to aid in any updates that may be needed in the Authorization Scheme and not have to update each individual Application that is using the that Authorization Scheme and update it only in the "main" application and push the update to the other Applications that are using it, the whole idea behind using Subscriptions right?
A question came up regarding deploying an Application that has Authorization Schemes that are Subscribed. The company is going to be using an automated deploying tool, I think it's called Jenkins, for deployments to the QA and Production environments.
How do the Authorization Schemes that are subscribed get updated when using an automatic deployment tool? Does and Admin have to then go into the "main" application and click the "Publish" button after deployment or is there some command line process that could be used during the deployment process that will "Publish" the Authorization Schemes without an Admin having to go into the "main" application and click the "Publish" button?
Thanks,
Joe

This post has been answered by InoL on Feb 18 2022
Jump to Answer

Comments

InoL

If you change anything that is shared, you push it to the subscribers in your development APEX Builder. In your case: when you change the authorization scheme in the master app, push it to the subscribing apps in dev, export all apps (or app components) and import these in the other environments (test and production).
So there is no need to go into APEX Builder in test and production to push these subscriptions. These environments shouldn't have builder access anyway.

Joe R

Inol,
Thank you for replying.
This approach is what I initially described to them (the client). They responded with not wanting to have to deploy all the applications (10 in total) when a change was made to an Authorization Scheme. So I was wondering if there was another approach that could be added to their automated deployment process, like a command line or similar, that could be used?
Thanks,
Joe

InoL
Answer

like a command line or similar
AFAIK: no. APEX Builder pushes the changes to the subscribers. I don't think there is a public API for that.

Marked as Answer by Joe R · Feb 18 2022
Joe R

Inol,
Thank you for confirming there's no other process than to go into the Scheme and Publish the updates.
I'll let them know. Honestly, I also asked how often they would make changes and they said not very often. So they had a concern that "remembering" that the updated Scheme would need to be published. I suggested we can put a comment in the Comments section on all the Schemes created to "remind" them what the process is. Now if they don't see or read it...well.
Thanks,
Joe

1 - 4

Post Details

Added on Feb 17 2022
4 comments
260 views