Applications of AP 2.0.1 has authorizationApplication as "AdministratorAdministration" - creating failure during /v1/regard-application

[IswaryaaS]

Applications with AP version 2.0.1 has application-name "AdministratorAdministration".

During registration of an application, when /v1/regard-updated-approval-status is being executed, /v1/regard-application is being sent to AccessAdministration application. As a callback to this /v1/regard-application, "/v1/inquire-oam-request-approvals" is being triggered to the registering application. During this step the below failure occurs.

This is because, as per specification of the service /v1/inquire-oam-request-approvals, the application name is defined as "find" (as in below picture). This rejects the incoming request when the given application-name is different from what is being configured in config file as AuthorizationApplication.

Proposals:

1. As a temporary workaround, we can update the application-name as "AccessAdministration" instead of "AdministratorAdministration" in the business applications having ApplicationPattern version 2.0.1 before registration.
2. Shall we make the application-name defined as "find or update" instead of "find" for the services /v1/inquire-oam-request-approvals and /v1/inquire-basic-auth-approvals service, so that in case any application-name is changed, the application name could be updated accordingly.

• if the above proposal is accepted, similar changes shall be considered for the following services as well.
  • /v1/redirect-service-request-information
  • /v1/redirect-oam-request-information
  • /v1/redirect-topology-change-information

[openBackhaul]

Workaround (proposal #1) shall be applied wherever required.
Changed for "find or update ..." at all five listed services.