Solved: Target Client Configuration Not Found (Easy Guide)

The current system configuration does not allow the requested. We're getting the matching client config not found error log. On our gateway / agent config, we have defined the remote okta ldap group as a source user. When we remove this to any. Navigate to network > globalprotect > gateway, click the gateway name > agent > client settings > config selection criteria tab.

On our gateway / agent config, we have defined the remote okta ldap group as a source user. When we remove this to any. Navigate to network > globalprotect > gateway, click the gateway name > agent > client settings > config selection criteria tab. Make sure the username that the gp app is trying to. To identify discrepancies between the username format used by the globalprotect client and that retrieved from the ldap server, refer to globalprotect is not getting the configuration when. Attaching failed report and new target configuration file(in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. You'll want to look at what you defined under gateway / agent / client settings and ensure that the auth'd client will match a config there. The (subtype eq globalprotect) filter on the system. 'matching config not found' means that you can't find a configuration for that user, investigate your config and group mappings.

Make sure the username that the gp app is trying to. To identify discrepancies between the username format used by the globalprotect client and that retrieved from the ldap server, refer to globalprotect is not getting the configuration when. Attaching failed report and new target configuration file(in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. You'll want to look at what you defined under gateway / agent / client settings and ensure that the auth'd client will match a config there. The (subtype eq globalprotect) filter on the system. 'matching config not found' means that you can't find a configuration for that user, investigate your config and group mappings. Or if you have set the gateway to only serve some geolocation. The error indicates that connecting user does not match any of the user config you have defined. First you need to identify if the error is returned by gp portal or gp gateway. The issue i am having is that when trying to connect internally i am getting not authorized message from the client.

Attaching failed report and new target configuration file(in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. You'll want to look at what you defined under gateway / agent / client settings and ensure that the auth'd client will match a config there. The (subtype eq globalprotect) filter on the system. 'matching config not found' means that you can't find a configuration for that user, investigate your config and group mappings. Or if you have set the gateway to only serve some geolocation. The error indicates that connecting user does not match any of the user config you have defined. First you need to identify if the error is returned by gp portal or gp gateway. The issue i am having is that when trying to connect internally i am getting not authorized message from the client.

Kindly provide the target configuration file for spc5746cbmku6, if you have. You'll want to look at what you defined under gateway / agent / client settings and ensure that the auth'd client will match a config there. The (subtype eq globalprotect) filter on the system. 'matching config not found' means that you can't find a configuration for that user, investigate your config and group mappings. Or if you have set the gateway to only serve some geolocation. The error indicates that connecting user does not match any of the user config you have defined. First you need to identify if the error is returned by gp portal or gp gateway. The issue i am having is that when trying to connect internally i am getting not authorized message from the client.

The issue i am having is that when trying to connect internally i am getting not authorized message from the client.