Problem:
The rules file does not allow a way to specify scope for the client in the open id flow
Solution:
Provide a property in the ID Token Attestation class to specify a scope value that augments the required openid value
Validation:
Unit test to ensure the scope value propogates and that existing rules are backwards compatible
Type of change:
[x] Feature work
[ ] Bug fix
[ ] Documentation
[ ] Engineering change
[ ] Test
[ ] Logging/Telemetry
Risk:
[ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes)
[ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features)
[x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes)
Work Item links:
Please include here links for this work item, or deferred work, or related work. E.g. if the refactoring is too big to fit in this PR, or the localized strings need to be updated later, please link the TODO work items here.
Documentation Links:
Please include here links to any related background documentation for this PR.
Problem: The rules file does not allow a way to specify scope for the client in the open id flow
Solution: Provide a property in the ID Token Attestation class to specify a scope value that augments the required openid value
Validation: Unit test to ensure the scope value propogates and that existing rules are backwards compatible
Type of change:
Risk:
Work Item links: Please include here links for this work item, or deferred work, or related work. E.g. if the refactoring is too big to fit in this PR, or the localized strings need to be updated later, please link the TODO work items here.
Documentation Links: Please include here links to any related background documentation for this PR.