Skip to content
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

Authpolicy with // double slashes not working #644

Open
enov opened this issue Mar 13, 2024 · 3 comments
Open

Authpolicy with // double slashes not working #644

enov opened this issue Mar 13, 2024 · 3 comments
Assignees

Comments

@enov
Copy link

enov commented Mar 13, 2024

Describe the bug
Authpolicy with // double slashes not working. When we want to secure /api but allow /, Citrix allows connections to everything under //* (for ex: //api/v1/ping). To deny //* we are adding // to the paths along with /api but it's not working.

Slack Channel
Invitation requested.

To Reproduce

  1. Add an auth policy with the following spec:
spec:
  authentication_policies:
    - provider:
        - jwt
      resource:
        method:
          - GET
        path:
          - //
          - /api
    - provider: []
      resource:
        method:
          - GET
        path:
          - /
  1. Version of the Citrix Ingress Controller: NS13.0 92.21.nc
  2. Version of MPX/VPX/CPX: ADC VPX 200 (?)
  3. Environment variables (minus secrets): n/a

Expected behavior
We would like to see //* auth policy enabled when // is added to the paths.

Logs
n/a

Additional context
Add any other context about the problem here.

@arijitr-citrix arijitr-citrix self-assigned this Mar 19, 2024
@arijitr-citrix
Copy link
Collaborator

Can you please provide the below information?

  1. CIC pod logs during the authpolicy creation
  2. CIC version. The version mentioned is of NetScaler and not CIC
  3. Please provide the deployment yaml or helm chart values yaml of CIC

@ankits123
Copy link
Contributor

hi @enov can you please provide the information as mentioned above.

@enov
Copy link
Author

enov commented Apr 3, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants