Are there any standard approaches to verifying the...
# support-questions-legacyw
willb
05/12/2023, 2:26 PMAre there any standard approaches to verifying the user in .NET?
r
rp_st
05/12/2023, 2:29 PMHey @willb you can use any JWT lib to verify in .NET
w
willb
05/12/2023, 2:30 PMYeah was wondering if anyone had any suggestions of libraries to use. I'm assuming something using the JWKS endpoint is probably best?
I've found https://github.com/NetDevPack/Security.JwtExtensions
r
rp_st
05/12/2023, 2:49 PMYup. Jwks enpoint use is the way to go.
w
willb
05/12/2023, 5:59 PM@rp_st Is there any reason why I am getting a 404 on my JWKS endpoint?
willb
05/12/2023, 6:09 PMUpgrading to latest version, it seems to just hang
r
rp_st
05/12/2023, 6:23 PMI’m not sure what api you are querying. Could you give more details please?
w
willb
05/12/2023, 6:35 PM@rp_st It was a super weird issue, couldn't load dashboard or anything in my API. Created a new SuperTokens account and connected to a different core and it works
r
rp_st
05/12/2023, 6:36 PMhmm. That's odd
rp_st
05/12/2023, 6:37 PManyway, if the error comes again, please let us know
w
willb
05/12/2023, 7:27 PMGot it working and roles loading from the supertokens JWT 🙂
willb
05/12/2023, 7:36 PMJust one issue, when I make a request to my .NET API from my Vue app I seem to get a 401, when I make a request from Swagger it seems to work.
willb
05/12/2023, 7:36 PMThe sAccessToken cookie doesn't seem to be included when I call from my Vue app
willb
05/12/2023, 7:37 PMWhich is weird, because it is somehow included in Swagger on a different port
r
rp_st
05/12/2023, 7:37 PMWhat’s the api domain for your .net backend and what’s the value of apiDomain set on the frontend?
w
willb
05/12/2023, 7:39 PM.NET backend: http://localhost:5179
Vue frontend: http://localhost:3000
ST backend: http://localhost:8080
Frontend appInfo:
Copy code
appInfo: {
apiDomain: "http://localhost:8080",
apiBasePath: "/auth",
appName: "App",
},r
rp_st
05/12/2023, 7:46 PMYou might want to get the access token on the frontend and then add that as an authorisation bearer token to the request to your .NET backend
rp_st
05/12/2023, 7:47 PMCause the interception is only applied to the apiDomain
rp_st
05/12/2023, 7:47 PMNetwork interception*
w
willb
05/12/2023, 7:48 PMWhat seems so weird is how the token exists in Swagger which is on the 5179 port?
willb
05/12/2023, 7:48 PMIf I use a reverse proxy and have both on port 8080, will it then load from the cookie correctly?
r
rp_st
05/12/2023, 7:48 PMYes.
w
willb
05/12/2023, 7:48 PMI'll try that, thanks 🙂
willb
05/12/2023, 8:25 PMForgot to say, that worked. Thank you!
15 Views