Fri, Oct 11
Wed, Oct 9
I think the problem is confusion between this task, T231671 (epic), and T231693 (user story). They are both named similarly. The epic has other user stories, including T231699, which you moved from a subtask to a parent task of this epic task. I will swap them back and rename the epic to make it clear it includes the requirement of a warning.
This task is related to T228988 but does not block it.
OK, thanks. I'm moving it out of the MCR schema migration initiative to the general MCR initiative.
Is this task blocking MCR schema migration?
@daniel, you now have the epic as a subtask of the user story. It should be the other way around. Are we missing an engineering task here?
Tue, Oct 8
I updated the task description for clarity.
Mon, Oct 7
Whitelisting would be optional. It is useful in an enterprise environment, where one application in an enterprise serves as the authentication provider for another trusted application. That being said, I've seen that done at the OpenID Connect layer on top of OAuth 2.0 for the openid scope, not in general. I'd be interested in a Security perspective. @Reedy?
Is this task ready to be marked Resolved?
@mforns, got it! Thanks for the heads up!
Tue, Oct 1
Reopen if this is still happening.
@eprodromou We can discuss this in the next Feature Request meeting. IIRC, you were working on something adjacent to this.
We discussed this in Clinic Duty. The related task T225512 has been resolved. This task, while good to have, is not as high a priority at this point so isn't going to be worked on by CPT in the near term. I'm putting it in the CPT Icebox.
Thanks for the suggestion, @Aklapper. Done.