Open Ashi1993 opened 1 month ago
@Ashi1993 are you attaching any roles to any resource of an API created in APIM? Could you please share those details?
Hi @senthuran16,
We have added below to the swagger file we are publishing.
x-scopes-bindings:
accounts: Internal/subscriber
Regards, Ashirwada
Please find the swagger file we are deploying [1]
Hi @Ashi1993 ,
It looks like IS7 doesn't support roles that have /
in their name, therefore Internal/subscriber
is not being accepted. Confirmed this via IS7 Role Creation REST API, and the UI as well. I will check with the IS team and provide an update on this.
Hi @senthuran16,
We are kind of blocked due to this issue. Can you please prioritize this?
Regards, Ashirwada
Hi @Ashi1993 ,
Got to know from the IS team that, they are treating the old Internal/
roles as normal roles in IS7. I.e, Internal/subscriber
role in APIM should be created as subscriber
in IS7. The IS7 migration client also does the same [1]
Currently based on our IS7 KM connector implementation, we have tested PRIMARY/
roles, and those are saved as normal roles in IS7. I.e, PRIMARY/myrole
- which is shown as myrole
in APIM carbon console, will be created as myrole
in IS7.
If we simply rename Internal/rolename
as rolename
, and create a role in IS7, how it would collide with PRIMARY/
roles (as of our current implementation) is a problem. I'm waiting for a call with @SujanSanjula96 to understand how PRIMARY/
roles are handled in migration cases; he is stuck in a customer issue a.t.m.
I will update you once we arrive at a solution, apologies for the delay.
Hi all,
We had a call and decided to handle roles as follows:
manager
):
system_primary_manager
in IS7.system_primary_manager
will be assigned to primary user group manager .Internal/publisher
):
publisher
in IS7.I implemented this in the IS7KM connector, and tested the connector with Internal/
roles - it's working as expected.
However PRIMARY roles are giving an error, since IS7 doesn't allow creating roles that start with the name system_
externally. I'm checking this with the IS team, and we'll request a patch to handle this if required.
Description
We observe an error in the console when trying to configure the created API before publishing. We tried configuring schema validation, policies, endpoints and got the same error in the console even thought the configurations saving is successful. We have added the WSO2 IS 7 as the custom key manager.
Steps to Reproduce
Setup IS 7 as a key manager. Create an API. Cinfigure endpoint.
Affected Component
APIM
Version
4.4.0-Alpha
Environment Details (with versions)
No response
Relevant Log Output
Related Issues
No response
Suggested Labels
No response