Tutorial with no Login View and spring ressource-server
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java, spring-boot
- Domain
- authentication, documentation
Research direction
Start with the linked Vaadin security documentation and the HttpSecurity configuration shown in the issue. Determine how a Vaadin frontend behind an nginx-authenticated reverse proxy should use Spring's OAuth2 resource server and JWT support without a Vaadin login view, then document the required configuration and logout behavior as a tutorial.
Written by the indexing model from the issue text.
Description
Hi, I'm not sure where to put this, so here I am.
I'm developing a rather big micro service cloud application with dozen of services, two of whom have a vaadin frontend.
They are obviously behind a reverse proxy (nginx) which handles the authentication (forwards to an IDP).
In the documentation (https://vaadin.com/docs/latest/security/enabling-security) it states the requirement for a login view and a log out capability. I have the latter, but no vaadin log in view.
On the other hand I just wan't to configure the jwt security with spring using a ressource-server to check the provided bearer token.
Could you please provide a tutorial, how this is supposed to be configured?
I currently have this configuration, but am not sure, if this is correct.
@Override
protected void configure(final HttpSecurity http) throws Exception {
http.authorizeRequests().antMatchers(ACTUATOR_HEALTH_ENDPOINT).permitAll();
http.authorizeRequests().antMatchers(ACTUATOR_PROMETHEUS_ENDPOINT).permitAll();
super.configure(http);
http.cors()
.and()
.oauth2ResourceServer()
.jwt();
}
- Dominant language
- Java
- Stars
- 205
- Forks
- 194
- Avg merge
- 4h 53m
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vaadin/flow-crm-tutorial
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
vaadin/flow-crm-tutorial#314 · 1 comment ·
-
waiting for author
Difficulty 3/5 1-2 days Newbie friendliness 35/100
vaadin/flow-crm-tutorial#264 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
vaadin/flow-crm-tutorial#113 · 6 comments ·
All issues in vaadin/flow-crm-tutorial
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
checkstyle/checkstyle#22145 ·
Maintainers usually reply within 1 day
-
rset command throws NPE in ResultsFormat.guessSyntaxPossibly taken @Ostrzyciel claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
objectionary/eo#9593 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100