GlobalProtect Gateway Configuration - Different IP pool if BYOD is used

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.

GlobalProtect Gateway Configuration - Different IP pool if BYOD is used

L2 Linker

Hi,

I recently received the following business requirement. for some internal SSO applications to work correctly, they need to whitelist IP ranges to make SSO work as expected. If the user is logged in using a corporate laptop enrolled in Intune, they use a corporate user account and the SSO works after the VPN is established.

On the contrary, if the same user connects using the GlobalProtect client with the same user credentials, the SSO portal does not work as the user did not use a valid authenticated account against Azure AD (as it happens when the enrolled laptop).

 

The question is, is there a way to achieve this behavior? to get a different IP depending if the OS is corporate or not. I thought I could use HIPS profiles for this purpose but could not find the way.

I saw in the Gateway -->Agent ->client settings that I could filter by OS. Is there a way to add an additional OS like "Corporate OS". If I can achieve this, I could simply create two different Client Settings based on that OS.

 

any other ideas?

 

cheers

 

1 accepted solution

Accepted Solutions

L6 Presenter

Not sure, but I don't think you can do this with the Gateway alone. With Gateway->Agent->Client Settings you can create different profiles with different assigned IP pools based on user, OS, and source region/IP. But I don't see a way to select a profile by PC type.

 

Something else you could try is moving that decision back to the Portal and then creating 2 Gateways and use the Portal->Agent->Config Selection Criteria to choose which Gateway to connect the client to. There is an option there for machine certificate check, so you could have a default agent config that confirms a corporate machine cert is installed, and if not it fails to the second agent config which sends the client to the alternate gateway (with a different IP pool).

 

View solution in original post

2 REPLIES 2

L6 Presenter

Not sure, but I don't think you can do this with the Gateway alone. With Gateway->Agent->Client Settings you can create different profiles with different assigned IP pools based on user, OS, and source region/IP. But I don't see a way to select a profile by PC type.

 

Something else you could try is moving that decision back to the Portal and then creating 2 Gateways and use the Portal->Agent->Config Selection Criteria to choose which Gateway to connect the client to. There is an option there for machine certificate check, so you could have a default agent config that confirms a corporate machine cert is installed, and if not it fails to the second agent config which sends the client to the alternate gateway (with a different IP pool).

 

Thanks a lot @Adrian_Jensen 

I like your idea, my only problem with that approach is to create the second alternate gateway.

For that I tried to create that subinterface in the same interface where the main gateway is configured at the moment, and assign it a free public IP that we own.

when I tried the commit I received an error informing that both interfaces are in the same subnet (overlapping). I opened a ticket with our local partner to help us to solve this.

thanks a lot once again.

 

 

  • 1 accepted solution
  • 1529 Views
  • 2 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!