View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009302 | 10000-003: Address Space | Spec | public | 2023-12-04 19:15 | 2024-05-14 15:50 |
| Reporter | Jim Luth | Assigned To | Jeff Harding | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.02 RC1 | ||||
| Fixed in Version | 1.05.04 RC1 | ||||
| Summary | 0009302: 4.8.2 Well Known Roles - Clarify what 'valid non-anonymous credentials' are. | ||||
| Description | Spec needs to clarify what 'valid non-anonymous credentials' are. If 'valid non-anonymous credentials' include a trusted client certificate then a client using the anonymous user credential would have access to the AuthenticatedUser Role. If they don't then a client granted SecurityAdmin role via its certificate would not have access to the AuthenticatedUser Role unless it also provides a non-anonymous user token. Neither scenario is intuitive and would likely lead to IOP issues. | ||||
| Tags | No tags attached. | ||||
| Commit Version | 1.05.04 RC | ||||
| Fix Due Date | 2024-01-15 | ||||
| related to | 0008194 | closed | Jeff Harding | 10000-003: Address Space | 4.8.2 Well Known Roles - Clarify what 'valid non-anonymous credentials' are. |
| related to | 0009301 | closed | Matthias Damm | 10000-018: Role-Based Security | 4.8.2 Well Known Roles - Clarify what 'valid non-anonymous credentials' are. |
|
|
Proposal clarify that anonymous has no credential and is never authenticated and refer to "AuthenticatedUser Role" as the "Authenticated Role" and make it clear it is not always a User. |
|
|
need to remove the term 'anonymous user' and use 'anonymous role'. |
|
|
Updated to 4.9.1 to clarify that anonymous means no authentication at the user or application level. |
|
|
Need to add a new role "AuthenticatedApplication" |
|
|
Added new AuthenticatedApplication well know role. |
|
|
changed the name of the new Role to TrustedApplication. |
|
|
Agreed to text edited in Web Meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-04 19:15 | Jim Luth | New Issue | |
| 2023-12-04 19:15 | Jim Luth | Status | new => assigned |
| 2023-12-04 19:15 | Jim Luth | Assigned To | => Jeff Harding |
| 2023-12-04 19:15 | Jim Luth | Issue generated from: 0008194 | |
| 2023-12-04 19:15 | Jim Luth | Note Added: 0020475 | |
| 2023-12-04 19:15 | Jim Luth | Note Added: 0020476 | |
| 2023-12-04 19:15 | Jim Luth | Note Added: 0020477 | |
| 2023-12-04 19:15 | Jim Luth | Relationship added | related to 0008194 |
| 2023-12-04 19:16 | Jim Luth | Note Added: 0020478 | |
| 2023-12-04 19:16 | Jim Luth | Commit Version | => 1.05.04 RC |
| 2023-12-04 19:16 | Jim Luth | Fix Due Date | => 2024-01-15 |
| 2024-05-07 15:43 | Jeff Harding | Status | assigned => resolved |
| 2024-05-07 15:43 | Jeff Harding | Resolution | open => fixed |
| 2024-05-07 15:43 | Jeff Harding | Fixed in Version | => 1.05.04 RC1 |
| 2024-05-07 15:43 | Jeff Harding | Note Added: 0021167 | |
| 2024-05-14 15:21 | Jim Luth | Note Added: 0021188 | |
| 2024-05-14 15:21 | Jim Luth | Issue cloned: 0009551 | |
| 2024-05-14 15:23 | Jim Luth | Status | resolved => closed |
| 2024-05-14 15:23 | Jim Luth | Note Added: 0021196 | |
| 2024-05-14 15:49 | Jim Luth | Relationship added | related to 0009301 |
