MicroProfile Interoperable JWT RBAC 1.2 Compatible Certification Request - Payara Community 5.2021.10

eclipse / microprofile-jwt-auth

Apache License 2.0

106 stars 59 forks source link

MicroProfile Interoperable JWT RBAC 1.2 Compatible Certification Request - Payara Community 5.2021.10 #283

Closed bacehanural closed 4 months ago

bacehanural commented 2 years ago

[x] Organization Name ("Organization") and, if applicable, URL:
Payara Services Ltd.
[x] Product Name, Version and download URL (if applicable):
Payara Platform Community 5.2021.10 Release
[x] Specification Name, Version and download URL:
MicroProfile Interoperable JWT RBAC 1.2
[x] Public URL of TCK Results Summary:
MicroProfile TCK Results
[x] Any Additional Specification Certification Requirements:
No
[x] Java runtime used to run the implementation:

zulu 8

[x] Summary of the information for the certification environment, operating system, cloud, ...:

AWS, Ubuntu 20.04

[x] By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.
[x] By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

sberyozkin commented 2 years ago

Hi @bacehanural Thanks for opening this request, my understanding these requests have to be created once to support a given release, for example, for 1.2 it was #227, for 2.0 - #269.

@radcortez @Emily-Jiang Can you clarify please ?

Emily-Jiang commented 2 years ago

Thanks for opening this request, my understanding these requests have to be created once to support a given release, for example, for 1.2 it was #227, for 2.0 - #269.

What you mentioned is the minimum requirement for releasing a spec. This issue is to certify a runtime after the release. It is okay for a runtime to submit a CCR here to certify the support of a particular release of the corresponding spec. However, it will save time to just raise a CCR to cover all of MP 4.1 specs on the eclipse/microprofile repo. At the moment, we are standardising the TCK certification process here. Once MP WG agrees, we will publicise the process so that everyone can follow. Hopefully, we will settle this soon. You can leave this issue for now.

sberyozkin commented 4 months ago

I believe we can close this issue now, IMHO the list of open issues should be about fixing something in the MP JWT spec