Service Token = 301
I have a nice tunnel setup with zero trust. I have sub.domain.com pointing to http:localhost:port. (This points to a instance of dufs.) I can download an image with a curl consistantly. I want to add in a service token. I created the token, made an application and associated with sub.domain.com. When I curl for "the cookie" I get a 301 no matter what I try.
What could I be missing. Appreciate any insight.
5 Replies
301 means the token didnt work, whats your access policy rule look like? It should have Service Auth as the action
Ok, maybe this is where I am lost. I made the token and then created an application with a policy that requires that token.
Is this the wrong road?
Does the the Application Policy Action need to be set to Service Auth?
So now I get a webpage. Is the <template id="index-data"> The cookie?
cookie would be in a header
hmm
Can we walk through it?
Application>Add Police>Policy Name <name>>Action Service Auth> Include > Service Token><Token Name>
Added a require as well for testing and toggled 401
What is immediatly concerning is I can still curl my sub.domain.com and download image with no errors?
Seem to have it working now. The ol' -v in curl really helped me out. I am curious though. I self host vaultwarden. Is there a way to apply a service token to it? (Maybe better asked in a new thread.?)
I doubt it's possible