Tuesday, 2022-01-25

*** ministry is now known as __ministry00:06
dmendiza[m]#startmeeting keystone15:01
opendevmeetMeeting started Tue Jan 25 15:01:36 2022 UTC and is due to finish in 60 minutes.  The chair is dmendiza[m]. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'keystone'15:01
dmendiza[m]#topic Roll Call15:01
dmendiza[m]Courtesy ping for ayoung, bbobrov, crisloma, d34dh0r53, dpar, dstanek, gagehugo, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rodrigods, samueldmq, spilla, ruan_he, wxy, sonuk, vishakha,Ajay, rafaelweingartner, xek15:02
knikollao/15:02
d34dh0r53o/15:02
dmendiza[m]As usual, the agenda etherpad is over here: https://etherpad.opendev.org/p/keystone-weekly-meeting15:02
dmendiza[m]OK, let's get started15:03
dmendiza[m]#topic Review Past Meeting Action Items15:03
xeko/15:03
dmendiza[m]#link https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-01-18-15.00.html15:03
dmendiza[m]We didn't have any15:04
dmendiza[m]#topic Liaison Updates15:04
dmendiza[m]knikolla: any updates this week?15:04
knikollano updates, need to catch up15:04
dmendiza[m]You need some help with that?15:04
dmendiza[m]I need to catch up on Oslo stuff15:04
dmendiza[m]for Barbican15:04
dmendiza[m]I could definitely keep an eye out for Keystone stuff too15:05
knikollathanks! we used to have a rotating bug duty position which involved keeping up with mailing list, bugs, etc. we can bring that back. 15:06
dmendiza[m]Yeah, that sounds interesting.  I'm sure d34dh0r53 would want to help out too15:07
* dmendiza[m] nudges d34dh0r53 15:07
knikollathe etherpad is linked in the meeting agenda https://etherpad.opendev.org/p/keystone-l1-duty15:08
d34dh0r53yeah, that sounds like something I can help with15:08
dmendiza[m]Let's try to do that this week.15:09
dmendiza[m]I'll take this week, and we can do a handoff next week15:10
dmendiza[m]during this meeting15:10
dmendiza[m]#info dmendiza[m] is on L1 duty this week15:10
dmendiza[m]OK, moving on ...15:11
dmendiza[m]#topic Specs15:11
dmendiza[m]Let's start with OAuth 2.015:11
dmendiza[m]#link https://review.opendev.org/c/openstack/keystone-specs/+/81315215:11
dmendiza[m]Looks like knikolla has a +2 review on it15:12
dmendiza[m]maybe we can get gagehugo to take a look this week15:12
dmendiza[m]it would be awesome to get that landed so h_asahina can start work on that15:12
dmendiza[m]Moving on to S-RBAC15:14
dmendiza[m]#link https://review.opendev.org/c/openstack/governance/+/81515815:14
dmendiza[m]looks like the follow-up to the Yoga goals is still under review15:14
dmendiza[m]I need to go review this myself15:14
dmendiza[m]There's also two more specs that need review15:16
dmendiza[m]related to S-RBAC15:16
dmendiza[m]#link https://review.opendev.org/c/openstack/keystone-specs/+/81860315:16
dmendiza[m]> Describe the need for a default manager role15:17
dmendiza[m]and also15:17
dmendiza[m]#link https://review.opendev.org/c/openstack/keystone-specs/+/81861615:17
dmendiza[m]> Describe the need for a default service role15:17
dmendiza[m]Both will be needed for S-RBAC15:17
dmendiza[m]There's one more spec that is < 90 days old15:18
dmendiza[m]#link https://review.opendev.org/c/openstack/keystone-specs/+/61814415:18
dmendiza[m]> Reparent Projects15:19
dmendiza[m]I have not looked into that last one at all.  I'll try to catch up on specs this week15:20
dmendiza[m]#topic Open Discussion15:21
dmendiza[m]Any other topics before we move on to the Bug Review?15:21
dmendiza[m]OK, moving on ...15:26
dmendiza[m]#topic Bug Review15:26
dmendiza[m]#link https://bugs.launchpad.net/keystone/?orderby=-id&start=015:26
dmendiza[m]Hmm... Not sure how far back we need to look15:28
dmendiza[m]let's start with mid-december15:28
dmendiza[m]since it's been a while15:28
dmendiza[m]#link https://bugs.launchpad.net/keystone/+bug/195442515:28
dmendiza[m]> Administrator can't create trusts on behalf of users15:28
dmendiza[m]Interesting case15:32
dmendiza[m]I don't have any historical context to answer why admins are not allowed15:32
knikollaI know there are limitations with system scoped tokens when the operation requires a project_id in the context, but this bug seems to mention that this wouldn't be the case since all required parameters are in the request. 15:34
knikollaI don't have a strong opinion whether to allow admins to create trusts for users, or not. 15:35
dmendiza[m]Yeah, I was going to say, in the context of S-RBAC, a project-admin would be a persona that is used by an operator15:35
dmendiza[m]so it would make sense for an operator to allow the creation of trusts15:35
dmendiza[m]*to allow an operator to create them15:35
dmendiza[m]and maybe it also makes sense for a project-manager to be able to create trusts for users in their project?15:36
dmendiza[m]I'll take this bug15:39
dmendiza[m]Next 15:39
dmendiza[m]#link https://bugs.launchpad.net/keystone/+bug/195466515:39
knikollai'm a bit hesitant, just because a trust delegates permissions from a user to another user, and my spider sense is tingling when you're delegating someone else's permissions, even if you're an admin. 15:39
dmendiza[m]perhaps a better option would be to move the hard-coded deny to a policy15:40
dmendiza[m]then someone who wants to do it can create a custom policy for that trust endpoint15:41
knikollaI delegate to people with more of a security background than I have on this. 15:42
knikollaYou can accomplish a lot of what they're trying to do by using other mechanisms already. 15:42
knikollaGroups, new users, application credentials, etc. 15:43
knikollaI think this also the only mechanism that we have that allows impersonation, with the token actually getting the user_id of the trustor. 15:44
dmendiza[m]Hmmm... good points15:45
dmendiza[m]Maybe we can talk about it some more for the Friday reviewathon15:46
knikollasounds good15:47
dmendiza[m]OK, moving on to 15:47
dmendiza[m]>  default opt out from non-existing event (authenticate.failed) 15:47
dmendiza[m](linked above)15:48
dmendiza[m]Seems pretty straightforward15:48
dmendiza[m]looks like there may be a mismatch in queue names15:48
knikollaeven though there was a typo, we're still changing default behavior15:51
knikollaAt the very minimum it requires a release note15:51
knikollaOn the other hand of the spectrum we can update the config text to mention that only authentication failures are sent. 15:52
dmendiza[m]I think the issue is that we're using the string as defined in pycadf 16:00
dmendiza[m]#link https://opendev.org/openstack/keystone/src/branch/master/keystone/notifications.py#L587-L58916:00
dmendiza[m]which is defined as "failure"16:00
dmendiza[m]#link https://opendev.org/openstack/pycadf/src/branch/master/pycadf/cadftaxonomy.py#L7616:00
dmendiza[m]so we will never emit an event called "failed"16:01
dmendiza[m]In any case, we're out of time for the week16:01
dmendiza[m]we can pick this again next week16:01
dmendiza[m]thanks for joining, y'all!16:02
dmendiza[m]#endmeeting16:02
opendevmeetMeeting ended Tue Jan 25 16:02:14 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
opendevmeetMinutes:        https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-01-25-15.01.html16:02
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-01-25-15.01.txt16:02
opendevmeetLog:            https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-01-25-15.01.log.html16:02
*** colleen1 is now known as cmurphy19:59

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!