Windows AD Authentication to Oracle Datasource from Fabric Fails

[amoren]

We have some Oracle 19c datasources that use Oracle CMU for AD authentication to them.  When we use PowerBI Desktop to create a report it connects fine to the datasources.  However when we publish the report to Fabric and use the on-premise gateways to access the Oracle datasources, we keep getting "invalid credential" errors. If we use datasource credentials the connections work fine, but we prefer to use centrally managed AD credentials.  I also tried manually creating the connections without reports and get the same errors below.

"Unable to create connection for the following reason: Invalid connection credentials.

Details: <gateways> The credentials provided for the Oracle source are invalid. (Source at <oracledb>.)"

Has anyone successfully connected to Oracle CMU controlled datasources via on-premise gateways?  Both PowerBI Desktop workstations and Fabric gateways use OCMT for their Oracle client.

Thanks,

Adam

[v-menakakota]

Hi @amoren   ,
Thanks for reaching out to the Microsoft fabric community forum. 

It looks like the issue is related to how Windows AD authentication is handled through the on-premises data gateway. While Oracle CMU works fine with Power BI Desktop, the Fabric service authenticates through the gateway, which requires some additional configuration.
 

Here are a few suggestions that may help:
 Ensure that the gateway is running under a domain account that is recognized by your Oracle CMU setup. This           is important for Kerberos-based authentication to work properly.

 Some users have successfully configured DSNs with Kerberos or used Oracle Wallets mapped to the domain account for secure access.
Please go through the below link:
Solved: Issue when connecting fabric to oracle using pipel... - Microsoft Fabric Community

 

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka Kota 
Community Support Team

[v-menakakota]

Hi @amoren ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily. 

 
Thank you. 

[amoren · Accepted solution]

Solved.

We had to enable SQLNET settings in our sqlnet.ora file referenced by OCMT running on the gateway.

e.g.
SQLNET.AUTHENTICATION_SERVICES= (<our approved auth sources>)
SQLNET.KERBEROS5_CC_NAME = OSMSFT://
SQLNET.KERBEROS5_CONF="<Path to our krb5.conf>"