Hi,
I’m getting 401 Authorization Required error when login to Aurena in IFS cloud 22R1 SU6 based application which is newly created. I noticed that ifsapp-iam pod keep failing. What can I do next to fix the issue ?
I’ve attached the iam log here.
Regards,
Dilshani
Best answer by Charith Epitawatta
This was investigated through a case and R&D provided following steps to drop and recreate IFSIAMSYS schema.
Please note that this was a fresh installation coming from an upgrade, so there were no customer specific IAM configurations in the environment.
Run DROP USER ifsiamsys on db. This should drop the existing IFSIAMSYS schema.
SELECT *
FROM dba_objects
WHERE owner = 'IFSIAMSYS'
AND object_type = 'TABLE';
Hi
looking at the error it seems that one of the objects that IAM is trying to create already exists in the database. Was the database cloned from another database? Any chance there is another MT instance connecting to the same database? You can see if there is a another MT instance connecting to the database by querying v$session and checking the IP addresses of the database session to see if there is anything connecting from an IP address different from your new MT instance.
Cheers
+31This was investigated through a case and R&D provided following steps to drop and recreate IFSIAMSYS schema.
Please note that this was a fresh installation coming from an upgrade, so there were no customer specific IAM configurations in the environment.
Run DROP USER ifsiamsys on db. This should drop the existing IFSIAMSYS schema.
SELECT *
FROM dba_objects
WHERE owner = 'IFSIAMSYS'
AND object_type = 'TABLE';
+5Hi Charith,
We are having similar case upon completion of upgrade from old version of IFS to IFS Cloud 23R1. But when IFSADMIN attempted to login to IFS Cloud, after user authentication the application could not be loaded with the following error message. Similarly when we check the Pods, IFSAPP-CONNECT only running ½ instead of 2/2.
Do you mean, the corrective action is to do prepare DB like before we do the upgrade process after dropping IFSIAMSYS user? Then we just need to restart IFSAPP-IAM, then it should solve the probelm?
This was investigated through a case and R&D provided following steps to drop and recreate IFSIAMSYS schema.
Please note that this was a fresh installation coming from an upgrade, so there were no customer specific IAM configurations in the environment.
Run DROP USER ifsiamsys on db. This should drop the existing IFSIAMSYS schema.
SELECT *
FROM dba_objects
WHERE owner = 'IFSIAMSYS'
AND object_type = 'TABLE';
Thanks,
Sutoto
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.