-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GlobalProtect 1.2 Plugin fails to resolve after upgrading Palo Alto Firewall from 9.x to 10.1.x #15
Comments
we have multiple vsys and ip-user-mapping api is not working now 2022-05-11 14:25:20,559 : DEBUG - 26 - globalprotect_resolve.py : Resolve for GlobalProtect Connect App |
Temporaryly fixed by hardcoding ib globalprotect_library.py "OC_SHOW_IP_USER_MAPPING": We need to have a parameter for Vsys and pass on the method rather hardcording it "OC_SHOW_IP_USER_MAPPING": |
Forescout Team, Any plans to provide fix to the plugin. |
@ramganesh19 Does v 1.2.1 fix the issue here? |
Is there anyone found the solution? |
2022-05-11 14:28:56,141 : DEBUG - 347 - globalprotect_library.py : Return status: success
2022-05-11 14:28:56,141 : DEBUG - 348 - globalprotect_library.py : Return error:
2022-05-11 14:28:56,141 : DEBUG - 53 - globalprotect_resolve.py : Found gateway: <>.
2022-05-11 14:28:56,141 : DEBUG - 110 - globalprotect_resolve.py : In is_in_current_user_gateway
2022-05-11 14:28:56,141 : DEBUG - 111 - globalprotect_resolve.py : Check if gateway <> contains host <>
2022-05-11 14:28:56,141 : ERROR - 229 - globalprotect_resolve.py : No user mapping info found. No gateway info found.
2022-05-11 14:28:56,141 : DEBUG - 69 - script_runner.py : Ready to send response.
2022-05-11 14:28:56,142 : DEBUG - 72 - script_runner.py : Done with message.
The text was updated successfully, but these errors were encountered: