Do you have a timeline for C# .net 6 support?
# support-questions-legacys
SammyK
09/08/2022, 10:35 AMDo you have a timeline for C# .net 6 support?
r
rp_st
09/08/2022, 10:36 AMhey!
rp_st
09/08/2022, 10:36 AMnot yet. But probably sometime next year
rp_st
09/08/2022, 10:37 AMthat being said, you can still use us if you are open to running a separate node / golang or python process that integrates with our SDK
s
SammyK
09/08/2022, 10:39 AMIf I understand it correctly does the core still require a java runtime?
r
rp_st
09/08/2022, 10:39 AMyea. But we bundle all that into the binary / docker image
rp_st
09/08/2022, 10:39 AMso you don't need to explicitly setup java
rp_st
09/08/2022, 10:41 AMessentially setup a node / golang / python server which integrates our backend SDK containing your config. This would talk to the supertokens core. The frontend would call this node / python / golang process for auth related APIs.
Post login, the frontend gets a JWT which you can send to your c# backend.
s
SammyK
09/08/2022, 10:45 AMThanks, this might already be answered in your docs, but can it do session handling in a more traditional sense where you have a session key where the session values are not included in the token, but only available on the backend? I'm not sure we are allowed to use a system where the session values are also included in the "frontend" as we have critical data in the session.
r
rp_st
09/08/2022, 10:49 AMyea that is possible, for this, you would need to setup the node process on a different sub domain or a different path as the c# process - so that cookies can be attached in a way that they get sent to the c# backend as well.
When the cookies are sent to c#, then you can use this package to verify the session: https://github.com/supertokens/supertokens-dotnet-salad (community maintained package for session recipe)
s
SammyK
09/08/2022, 10:52 AMThanks!
5 Views