You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "zeroflag (via GitHub)" <gi...@apache.org> on 2023/05/24 11:07:01 UTC
[GitHub] [knox] zeroflag opened a new pull request, #756: KNOX-2898 - Reconsider the usage of sso.unauthenticated.path.list
zeroflag opened a new pull request, #756:
URL: https://github.com/apache/knox/pull/756
## What changes were proposed in this pull request?
Unauthenticated path list doesn't work when hadoop-jwt cookie exists but it's invalid / expired.
## How was this patch tested?
```xml
<topology>
<gateway>
<provider>
<role>federation</role>
<name>SSOCookieProvider</name>
<enabled>true</enabled>
<param>
<name>sso.unauthenticated.path.list</name>
<value>/favicon.ico;test;unsafepath</value>
</param>
</provider>
<provider>
<role>identity-assertion</role>
<name>Default</name>
<enabled>true</enabled>
</provider>
<provider>
<role>hostmap</role>
<name>static</name>
<enabled>true</enabled>
<param>
<name>localhost</name>
<value>sandbox,sandbox.hortonworks.com</value>
</param>
</provider>
</gateway>
<service>
<role>CM-UI</role>
<url>https://www.google.com</url>
</service>
</topology>
```
```bash
curl --cookie "hadoop-jwt=invalid" -k https://localhost:8443/gateway/sandbox/favicon.ico
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@knox.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [knox] zeroflag commented on pull request #756: KNOX-2898 - Reconsider the usage of sso.unauthenticated.path.list
Posted by "zeroflag (via GitHub)" <gi...@apache.org>.
zeroflag commented on PR #756:
URL: https://github.com/apache/knox/pull/756#issuecomment-1560979756
@moresandeep
If you omit the `hadoop-jwt` completely you can still bypass the authentication, I thought that was the goal to bypass the autnetication. However if your token expires you'll be redirected to the login page when accessing an unauthenticated path, such as /favicon.
In other filters such as `HadoopAuthFilter` we check the unauthenticated path first and do an early return if the path is there.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@knox.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [knox] zeroflag merged pull request #756: KNOX-2898 - Reconsider the usage of sso.unauthenticated.path.list
Posted by "zeroflag (via GitHub)" <gi...@apache.org>.
zeroflag merged PR #756:
URL: https://github.com/apache/knox/pull/756
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@knox.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [knox] moresandeep commented on pull request #756: KNOX-2898 - Reconsider the usage of sso.unauthenticated.path.list
Posted by "moresandeep (via GitHub)" <gi...@apache.org>.
moresandeep commented on PR #756:
URL: https://github.com/apache/knox/pull/756#issuecomment-1584443781
> @moresandeep If you omit the `hadoop-jwt` completely you can still bypass the authentication, I thought that was the goal to bypass the autnetication. However if your token expires you'll be redirected to the login page when accessing an unauthenticated path, such as /favicon.
>
> In other filters such as `HadoopAuthFilter` we check the unauthenticated path first and do an early return if the path is there.
I see, that makes sense. Thanks !
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@knox.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org