We are developing applications in a shared development environment but being deployed to different higher level environments. For OIDCCustomizations, some of the customizations only apply to some applications. So for example, some custom claims apply to APP1 but not APP2 and since APP1 and APP2 exist independently of each other I was curious how I could handle a modification to OIDCCustomizations that might get deployed with each of those apps. Should I just code various conditions based on app name and then use Service Actions in a dependent module to perform the custom action or should I clone OIDCCustomizations so there is no conflict? Also, how would updates to the Forge component version work if we already modified this module?How are people customizing OIDCCustomizations and dealing with that on an ongoing basis?
Hi @Dave Schuchman ,
The best approach would be to code in Dev the different logic per application and then have conditions to execute the corresponding code based on the application name.
The app name being sent to the service action is there for this particular use case of implementing custom logic per application, if needed.Regards,
If OIDCCustomizations needs to depend on another module we create, we should use Service Actions so if the dependency is only needed for APP1 (Environment 1) and not needed for APP2 (Environment 2) the deployment would still work (on APP2) without the dependency? I assume this is the normal advice for this situation?
That would be the best way to go about it.