Skip to content
MicroProfile JWT Build

Require that both RS256 and ES256 must be supported if the signature algorithm is not configured #401

Sign in to view logs

Require that both RS256 and ES256 must be supported if the signature algorithm is not configured

Require that both RS256 and ES256 must be supported if the signature algorithm is not configured #401

Triggered via pull request June 20, 2024 13:30
@sberyozkinsberyozkin
opened #333
sberyozkin:signature_algorithm_rs_rs256_es256
Status Success
Total duration 1m 10s
Artifacts –

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build with jdk 8
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build with jdk 8
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build with jdk 11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-java@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build with jdk 11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/