Palo Alto 2FA integration with OKTA not showing domain in username

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Palo Alto 2FA integration with OKTA not showing domain in username

L1 Bithead

Hello everyone,

 

We have successfully deployed the 2FA authentication for GP Portal and GP Gateway with OKTA SAML. In Okta we have the active directory integration for the user-mapping at the okta instance. 

 

The login and 2FA is working fine but when the users log's in, they are displayed at the monitor sometimes with the domain (domain\username) and sometimes only with the username so we can't apply policies with user or group restrictions.

 

Does anyone know which is the problem?

 

Regards,

Sergi

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

Hi @Sergi-Tost ,

 

I was waiting for someone with more Okta experience to reply, but no one has.

 

With SAML, the format of the username is determined by the IdP.  You would need to find something in the Okta cloud configuration to standardize the format.  Do you think it is simply an issue where sometimes the user logs in with the domain and sometimes not?

 

Thanks,

 

Tom

Help the community: Like helpful comments and mark solutions.

View solution in original post

3 REPLIES 3

Cyber Elite
Cyber Elite

Hi @Sergi-Tost ,

 

I was waiting for someone with more Okta experience to reply, but no one has.

 

With SAML, the format of the username is determined by the IdP.  You would need to find something in the Okta cloud configuration to standardize the format.  Do you think it is simply an issue where sometimes the user logs in with the domain and sometimes not?

 

Thanks,

 

Tom

Help the community: Like helpful comments and mark solutions.

Cyber Elite
Cyber Elite

Hello,

Also check with the vendor as they had a recent breach. Make sure your stuff is safe and protected.

 

Regards,

Hello TomYoung,

 

Yes the problem was at Okta side. We performed a custom type format for the user when sending to the Firewall.

  • 1 accepted solution
  • 675 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!