View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009440 | 10000-012: Discovery | Spec | public | 2024-02-26 15:58 | 2024-05-07 16:54 |
| Reporter | Peter Wehrfritz | Assigned To | Randy Armstrong | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | reopened | ||
| Product Version | 1.05.03 | ||||
| Fixed in Version | 1.05.04 RC1 | ||||
| Summary | 0009440: CredentialSecret format for UserName/Password | ||||
| Description | The UpdateCredential method of the KeyCredentialConfigurationType has a CredentialSecret argument of type ByteString. Depending on the used SecurityPolicyUri, this might be encrypted or not. If it is encrypted one can decrypt it as described for the EncryptedSecret in Part 4. No matter if it is encrypted or not. At the end you have an (decrypted) ByteString. How do you get the UserName/Password pair from that ByteString, which is needed for example for a Broker? | ||||
| Tags | No tags attached. | ||||
| Commit Version | 1.05.04 RC | ||||
| Fix Due Date | |||||
| related to | 0009533 | closed | Randy Armstrong | KeyCredentialConfigurationType does not expose the CredentialId |
|
|
Only the password is encrypted. Randy will check the spec to be sure this is clear. |
|
|
Ok, I see, and where can I find the Username for the broker authentication? |
|
|
Is maybe the CredentialId actually the user name? |
|
|
Added text to 9.5.6 The credentialId is the identifier, such as a user name, which often needs to be presented when using the credentialSecret. |
|
|
The clarification must be added also to 8.6.6 UpdateCredential for the description of argument 'credentialId' |
|
|
Added CredentialId Property to KeyCredentialConfigurationType. |
|
|
Agreed to changes edited in Web meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-26 15:58 | Peter Wehrfritz | New Issue | |
| 2024-02-27 16:27 | Jim Luth | Note Added: 0020862 | |
| 2024-02-27 16:27 | Jim Luth | Assigned To | => Randy Armstrong |
| 2024-02-27 16:27 | Jim Luth | Status | new => assigned |
| 2024-02-27 16:40 | Peter Wehrfritz | Note Added: 0020865 | |
| 2024-02-28 14:16 | Peter Wehrfritz | Note Added: 0020876 | |
| 2024-03-02 18:41 | Randy Armstrong | Status | assigned => resolved |
| 2024-03-02 18:41 | Randy Armstrong | Resolution | open => fixed |
| 2024-03-02 18:41 | Randy Armstrong | Note Added: 0020888 | |
| 2024-05-03 13:14 | Matthias Damm | Status | resolved => feedback |
| 2024-05-03 13:14 | Matthias Damm | Resolution | fixed => reopened |
| 2024-05-03 13:14 | Matthias Damm | Note Added: 0021158 | |
| 2024-05-03 13:19 | Matthias Damm | Relationship added | related to 0009533 |
| 2024-05-07 16:54 | Randy Armstrong | Status | feedback => resolved |
| 2024-05-07 16:54 | Randy Armstrong | Fixed in Version | => 1.05.04 RC1 |
| 2024-05-07 16:54 | Randy Armstrong | Note Added: 0021178 | |
| 2024-05-07 16:54 | Jim Luth | Status | resolved => closed |
| 2024-05-07 16:54 | Jim Luth | Commit Version | => 1.05.04 RC |
| 2024-05-07 16:54 | Jim Luth | Note Added: 0021180 |
