-
Notifications
You must be signed in to change notification settings - Fork 188
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
Use proper AUTH_URL values in next.config.js and AuthProvider #1954
Conversation
@@ -28,7 +28,7 @@ API_VERSION=v1 | |||
# Auth Service | |||
################################################################################ | |||
|
|||
# Auth Service Port (default is 4444) | |||
# Auth Service Port (default is 7777) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't feed discovery use 7777?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It did, but I've now updated it. We had two servers on the same port (auth was always on 7777 so it wasn't available when Tony chose it).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@humphd said we should test this on master
Deal with conflicting port 7777
Rebased to pickup the posts changes on master, I need two more reviews? I'd love to get this in soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need to merge to see if this works, but I tested locally and it worked just fine
Awesome, thanks! |
@manekenpix and @HyperTHD noticed a few bugs in the way the staging auth fix was being done. This corrects the problems by properly defining the
AUTH_URL
for next's build, and using it in theAuthProvider
.