Description
TryOut console always shows only "Resident key manager". Selection list never appears.
See "Steps to reproduce" for detailed description.
Steps to Reproduce
Use ACP 4.6.0 (scalable installation model with separate TM and UGW). Running
Configure New key manager in admin portal (only Keycloak tested)
Allow all key managers in API Runtime page in Publisher or select new key manager. It doen't matter, result will be the same
Subscribe to api and generate keys in new key manager
Go to Try out API console and try to get a token
You will see statically selected resident key manager instead of drop-down list of key managers.
I investigate Frontend API calls and found, that both key managers are correctly reported at /api/am/devportal/v3/key-managers endpoint.
I investigate JS scripts at frontend and found, that filtering of key managers list, received from backend, is always targeted at "Resident Key Manager". Maybe am'm wrong here, I'm not good at js.
It looks, like frontend bug.
Version
4.6.0
Environment Details (with versions)
No response
Description
TryOut console always shows only "Resident key manager". Selection list never appears.
See "Steps to reproduce" for detailed description.
Steps to Reproduce
Use ACP 4.6.0 (scalable installation model with separate TM and UGW). Running
Configure New key manager in admin portal (only Keycloak tested)
Allow all key managers in API Runtime page in Publisher or select new key manager. It doen't matter, result will be the same
Subscribe to api and generate keys in new key manager
Go to Try out API console and try to get a token
You will see statically selected resident key manager instead of drop-down list of key managers.
I investigate Frontend API calls and found, that both key managers are correctly reported at /api/am/devportal/v3/key-managers endpoint.
I investigate JS scripts at frontend and found, that filtering of key managers list, received from backend, is always targeted at "Resident Key Manager". Maybe am'm wrong here, I'm not good at js.
It looks, like frontend bug.
Version
4.6.0
Environment Details (with versions)
No response