Oracle Analytics Cloud and Server
OAC: "Connection failed 401: Unauthorized" When Trying To Open The RPD in Cloud Mode
Hello Experts,
We're getting OAC: "Connection failed 401: Unauthorized" error while opening the RPD online in Cloud Mode, has anyone faced this issue? Referred Doc ID 2609004.1 but we're already using non federated user.
Please suggest.
Answers
-
Hi Saurabh,
Please check if you are putting the correct details.
User: your non federated email id
password: your login pwd
hostname :host_name till .com except http/https
SSL - trust Store by default
password:changeit
-
Hi Alok, credentials are correct, I'm able to deploy the RPD using the same.
-
Hi Saurabh,
For online cloud mode you have to keep sqlnetora file in the windows path where rpd is installed. Please see if the sqlnet ora file is placed and the path in sqlnet.ora file is correctly pointing to the wallet.
<rpdhome>/domains/bi/config/fmwconfig/bienv/core
Regards,
Sunil
-
Hi Saurabh ,
Can you please check the OAC client version is latest one . This issue comes when we use an older version.
Thanks
Anirban
-
Hi Saurabh ,
Please check the following document as well, it talks about Native OCI admin user having Multi Factor Authenticator (MFA) enabled. This could be possibility , if MFA not enabled then you can ignore.
Thanks.
-
Thanks Narayanan, MFA is not enabled in our scenario.
-
Saurabh ,
Did you check the version of OAC client tool . Is it latest one ?
Thanks
Anirban
-
Current version is Oracle BI Administration Tool Version 12.3.1.0.0. RPD Version - 356
I'll update to latest version and get back to you.
Thanks,
Saurabh Jaiswal
-
Hi Saurabh,
Does your user have Admin privileges. If not, it needs to have BIDataModelAuthor App Role.
-
Yes, User is part of BI Service Administrator role and its a native OCI User (Non federated)
-
Hi,
We have experienced the same problem with the login in my organization two weeks ago. After updating to the latest version of OAC client tools 6.7 July 2022, the issue was solved and any user had any problem with the log in again
-
Yeah ,even this issue happened to us also . After upgrading to the latest version, this issue didn't come up
-
No luck :-( even after updating to latest version 12.3.3.0.0 Repository version 356 still getting the same "Connection failed: 401: Unauthorized" error message
-
Hi Saurabh,
This could be because of Credentials expired of the native IDCS user. Please log in to IDCS using the user created and see if the credentials have expired or not. If yes, then reset it. It would start working.
The second scenario when this happens is if someone has already opened in cloud mode. Then also you get this error if you try to open it at the same time. Please check if any of the above solutions works for you.
-
Can you please refer the following doc ids,
Few points from these docs are already mentioned by few members, but can you please ensure all the points mentioned in the doc are followed.
