Skip to content

JwtSecurityProviderIntegrationTest: Jwt token provider server listening on 127.0.0.1 #2302

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

JwtSecurityProviderIntegrationTest: Jwt token provider server listening on 127.0.0.1 #2302

wants to merge 1 commit into from

Conversation

akatona84
Copy link
Contributor

Summary

  1. Why: VPN can mess up things when the server is bound to the actual ip address (most likely the local network ip)
  2. What: binding to 127.0.0.1 makes it work everywhere

Categorization

  • documentation
  • bugfix
  • new feature
  • refactor
  • security/CVE
  • other

@akatona84
JwtSecurityProviderIntegrationTest: Jwt token provider server listeni…
ae2438f 
…ng on 127.0.0.1

VPN can mess up things when the server is bound to the actual ip address (most likely the local network ip)

Signed-off-by: Andras Katona <[email protected]>
kyguy
kyguy approved these changes Sep 16, 2025
View reviewed changes
Copy link
Contributor

@kyguy kyguy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
2 more reviewers

@viktorsomogyi viktorsomogyi viktorsomogyi approved these changes

@kyguy kyguy kyguy approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@akatona84 @viktorsomogyi @kyguy