Create OAuth2/OIDC Node to allow same authentication methods used and supported by our own OpenID Connect provider and clients (OPENAM-16314) [OPENAM-17491] Manually test PKI Created: 2021-03-03 Updated: 2021-03-08 Resolved: 2021-03-08 |
|
Status: |
Closed |
Project: |
|
Component/s: |
|
Affects Version/s: |
None |
Fix Version/s: |
Type: |
Sub-task |
Priority: |
Major |
Reporter: |
Assignee: |
||
Resolution: |
Fixed |
Votes: |
0 |
CustomerRFE, NEWTON |
|||
Remaining Estimate: |
Not Specified |
||
Time Spent: |
Not Specified |
||
Original Estimate: |
Not Specified |
1|i03vlc: |
|
AM 2021.02 - Water Turbine, AM 2021.03 - Chess, AM 2021.04 - Mariners Compass |
Comments |
|
Comment by Alun Daley [ 2021-03-03 ] |
Test Cases Mapping new secret id exposes new jwk at RP jwk uri Mapping new secret id and selecting TLS_CLIENT_AUTH in client config facilitates AM sending client certs to OP and successfully obtaining an id/access token Lack of new secret id mapping means no jwk exposed at jwk URI Lack of new secret id mapping and selecting TLS_CLIENT_AUTH in client config results in no client certs being sent |
Comment by Alun Daley [ 2021-03-04 ] |
https://drive.google.com/file/d/1yy2KfgGX7ssb5xEQQN7smN2sjE024fZD/view |
Generated at Fri Dec 03 17:49:19 UTC 2021 using Jira 8.20.1#820001-sha1:6d4b94dbcc29d26a5651b231dd69e39cd4357315.
11132015 GROUP FEB UNLAM & DIPERLUAS CREATED 081210481729 TERIMAKASIH
17 FOR DISCUSSION PURPOSES ONLY CREATED ON 8222006 53100
19 DOES ‘WANTING THE BEST’ CREATE MORE STRESS? THE
Tags: allow same, oauth2oidc, methods, create, allow, authentication