Java playframework: add support for oauth2 accesstoken validation

[bflamand]

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  For Windows users, please run the script in Git BASH.
• File the PR against the correct branch: master (5.3.0), 6.0.x
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
  @JFCote

[bflamand]

There is currently an issue when "useInterfaces: false". This is why one of the build steps failed. I will fix this.

[bflamand]

Can someone please take a look at reviewing/merging this?
technical committee: @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @nmuesch (2021/01)

[JFCote]

LGTM

[JFCote]

@bflamand Can you update your branch. It should fix the Docs up to date and Samples up to date test.

[bflamand]

yep, I was already on this...

[JFCote]

@bflamand not sure why it's not passing but it's not your fault since you generated the related samples. I will let the others from the technical committee validate this and merge.

@bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @nmuesch (2021/01)

[bflamand]

I agree @JFCote... I really generated all playframework samples, etc.
I also tried to generate everything outside of playframework files, but got into issues with unix vs windows file path everywhere. So I reverted my last push. Hopefully someone can help...
The differences seams to be related to the version that has changed from "(5.3.1)." to "5.4.0-SNAPSHOT" but someone has forgot to update generation for all files. I tried to do it on my side, but was not able to because of the aforementioned issue of unix vs windows paths...

[wing328]

CircleCI tests passed via https://app.circleci.com/pipelines/github/OpenAPITools/openapi-generator/14726/workflows/136a27bb-d711-4d20-98bf-755961c380d0/jobs/28397

[wing328]

@bflamand thanks for the PR. My only suggestion is regarding the following:

    private static final String X_JWKS_URL = "x-jwksUrl";
    private static final String X_TOKEN_INTROSPECT_URL = "x-tokenIntrospectUrl";

Ref: https://github.com/OpenAPITools/openapi-generator/pull/10901/files#diff-7ae256bbbecfb39c7b23e50a2835712533d614aa3c5fd31a68cb08e0651203f3R48

Can we use kebab-case instead as that's the convention we've in this project? i.e.

    private static final String X_JWKS_URL = "x-jwks-url";
    private static final String X_TOKEN_INTROSPECT_URL = "x-token-introspect-url";

Please feel free to update it in a separate PR as I'll merge this one for the time being.