...
| Info |
|---|
It is seen in recent deployments of IDA services that after a fresh deployments the the keys generated seems to have some issues resulting in errors like “No unique alias“ or “No such alias“. |
Solution
This is issue due to same key below reasons:
“No unique alias“: Duplicate keys (same AppID and RefID) getting inserted due to the IDA services starting in parallel.
To fix this issue follow the below steps:
Stop IDA services
In the Key Alias table of IDA DB remove any Duplicate entries of key alias, especially KERNEL SIGN.
Start one IDA service such as authentication-internal-service, after it is up then start other services. The first service will create an entry of the key alias, then other service started later will pick it, avoiding creation of duplicate key.
To prevent the issue altogether, start the IDA services one by one after a fresh deployment, it can be started in any order.
...
The first service needs to be completely started before starting the other services.
...
“No such alias“: The key for IDA AppID and gets created in Internal Auth service (using get public key API), but the same key is not getting loaded to other Auth services due to some issue in SoftHsm over http.
To fix this issue follow the below steps:
It is assumed the key for IDA AppID is already inserted in IDA DB.
Just restart the IDA services. Now the key for IDA will be loaded by the all services.
These issues will be addressed in forth coming release.
...