Closed 2FromField closed 2 months ago
Hello @2FromField,
Thank you for taking the time to report.
So you're saying we must enter name: policy
and token claim name: policy
?
I though it would fallback to the the name if not provided...
Absolutely, in my case it was necessary for the whole thing to work properly. Without this information properly indicated in this field, it didn't work. The policy didn't appear in the JWT token and therefore didn't allow the link between onyxia and minIO to work.
Thank you again for reporting, sory about the time it must have take you to find the issue.
I've added the missing step:
Perfect !
By the way I saw that you've created a nice theme!
How did you manage to develop it? Because as far as I know it was broken until yesterday. At least the .env.local.yaml
didn't work when using any #
character...
Ahah thank you very much!
I was inspired by your video tutorial: https://www.youtube.com/watch?v=NrVuVXsbloA
I simply implemented my onyxia-values.yaml
file in the web/env
section with the elements that can be modified. That's all there is to it.
You mean the .env.local.yaml? This confuse me because I tried to create a theme yesterday and I realized that it was broken since the Vite migration. 🤔
I'm happy that it worked for you, I just can't figure out how...
Anyway, have a nice day.
Follow the the Onyxia's v8 documentation on: https://docs.onyxia.sh/admin-doc/readme/data-s3. My “My Files” tab was not working due to a jwt token not containing the policy.
After following the Onyxia v8 documentation: https://docs.onyxia.sh/admin-doc/readme/data-s3. My “My Files” tab was not working due to a jwt token not containing the policy. To solve this problem, all I had to do was fill in the “Token Claim Name” field : “policy” on Keycloack, in the client tab : “onyxia-minio/onyxia-minio-dedicated/policy”.
This step is not mentioned in the documentation:
Joey BRUNO.