-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using react-adal with Server Side Rendering(Next.js) #67
Comments
no because clientId si just tell MS azure which AzureWebApp is going to login. there is no other way. authentication is from user pc to Azure not your server to Azure - it is a SPA application |
hum, if your full app is protected under login, it is unuseful to render before login. anyway if your app has just only a private section, then probably i will update the lib with a check on window object |
@M0W93 try v0.4.23 please share feedback if it is ok on SSR |
Thanks a lot for your effort. |
Hello @salvoravida,
on react-adal/lib/adal.js:141 |
@M0W93 try 0.4.24 |
Hi, I tried to use it in my sample app but I am not sure how to set it up?
My Component Code:
|
@saostad it should be fixed on v0.5.0 let me know your feedback! |
React adal latest version is not compatible with react 18 right? |
Hello,
actually im trying to use react-adal with Next.js, but because of the ´window´ reference in the library it isn't possible to use it with SSR.
Correct me if im wrong but isn't it insecure to deliver the whole adalConfig (with clientId) to the browser?
The text was updated successfully, but these errors were encountered: