16:00:24 #startmeeting keystone 16:00:25 Meeting started Tue Jul 31 16:00:24 2018 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:28 The meeting name has been set to 'keystone' 16:00:34 #link https://etherpad.openstack.org/p/keystone-weekly-meeting 16:00:36 agenda ^ 16:00:41 ping ayoung, breton, cmurphy, dstanek, gagehugo, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rodrigods, samueldmq, spilla, aselius, dpar, jdennis, ruan_he, wxy, sonuk 16:01:19 o/ 16:01:21 o/ 16:01:22 o/ 16:01:49 o/ 16:02:03 in another meeting today so will review the minutes after y'all 16:02:25 o/ 16:02:38 we don't have a lot on the agenda today 16:02:54 so likely going to be a quick meeting unless people have things for open discussion 16:03:04 #topic announcements 16:03:12 #info we cut rocky-3 last week 16:03:24 so - that means we're effectively in RC period 16:03:31 and we're in string freeze 16:03:46 just things to be aware of while reviewing and working through bugs 16:03:58 #topic reviews 16:04:06 i think there are still flask reviews that need eyes 16:04:12 and same with the token provider API refactor 16:04:22 does anyone have anything else they want eyes on? 16:05:01 https://review.openstack.org/#/c/580780/ if anyone has time 16:06:02 gagehugo: sounds good - i think colleen had some comments on the early revision of that 16:06:14 were we able to determine if it was actually a bug? 16:06:33 flask stuff is well on the way, but auth has been a beast 16:06:39 just because os-federation 16:07:10 * kmalloc has to fix a patch then go back and finish porting auth 16:07:31 kmalloc: the os-revoke patch i had that you rebased appears to be failing tests 16:07:37 but that's later in the chain 16:08:15 lbragstad: I think I put it in the bug report, but we were seeing logins to horizon with random uuids in the notifications, imo those should be the user id as the initiator 16:08:29 initiator id* 16:09:05 lbragstad: that is becasue of the previous one 16:09:16 lbragstad: or two patches before, the fix will solve that as well. 16:09:35 gagehugo: ack 16:09:49 kmalloc: ok - sounds good 16:10:03 but it happens for any identity.authentication event afaik 16:10:12 i'm in the middle fixing some of my development environments, but i should be able to get around to reviewing it today 16:11:09 wxy| was super helpful with the test case btw, it was kinda confusing at first 16:11:18 awesome 16:12:04 #topic open discussion 16:12:15 that's about all i had... just a few reviews really 16:12:22 does anyone have anything they'd like to bring up? 16:12:41 i hate code that calls across controllers. 16:12:53 e.g. federation controller -> auth controller 16:12:56 https://bugs.launchpad.net/keystone/+bug/1779205 has an interesting comment on it (#68) 16:12:56 Launchpad bug 1779205 in OpenStack Identity (keystone) rocky "[OSSA-2018-002] GET /v3/OS-FEDERATION/projects leaks project information (CVE-2018-14432)" [Critical,Fix released] - Assigned to Lance Bragstad (lbragstad) 16:12:56 please don't do that. 16:13:16 well - we already did :) to fix ^ 16:13:21 lbragstad: the comment is exactly why i recommended removing the "endpoint being enabled" part of the message 16:13:52 lbragstad: no, we didn't there, i mean we do things like federation controller calls auth.authenticate_for_token 16:14:01 oh 16:14:02 controllers should not call another API like that 16:14:21 because you get double enforcement issues 16:14:30 a controller's logic should render the whole response. 16:14:31 i suppose the messes with the routing 16:14:41 er dispatching with flask 16:14:46 if you need to share code, share it don't call another controller 16:14:55 yeah i've been unwinding os-federation, it's a beast. 16:15:04 i think we do this elsewhere too. 16:15:32 lbragstad: anyway the comment on #1779205 is consistent with the confusion of what enabling the endpoint means 16:16:06 lbragstad: we should have just eliminated that part of the impact statement, 99% of deployments don't muck with that stuff. 16:16:22 can't you set the policy to "@" to blacklist it? 16:16:27 you can. 16:16:37 but almost no one does that kind of stuff. 16:16:55 not for federation where they dind't deploy say shib or federated auth 16:17:23 maybe we should have said: With default policy.json for entry get_projects_for_user 16:17:29 erm list_projects_for_user* 16:17:37 oh - sure 16:17:58 the code / fixes did the right thing 16:18:16 and it was thoroughly tested 16:18:18 the comment is regarding the impact statement. 16:18:26 and pre-patch testing afaict 16:18:58 abhi was confirming what kristi confirmed early on, non-federated tokens got complete lists 16:18:59 :) 16:19:24 but confused because the impact statement was not well worded for that sentence. 16:19:33 basically.. we're all good nothing to see here :) 16:20:19 ack 16:20:26 anything else we want to discuss? 16:21:09 * kmalloc wants to discuss how the meeting can end so he can go make coffee. 16:21:46 ++ we can end early... my home lab is completely hosed right now and i'm trying to fix it =/ 16:22:02 lbragstad: my home lab is ... torn apart, will be fixed later this week. 16:22:09 wanna fix mine too? 16:22:12 ;) 16:22:13 (like, it's missing computers right now) 16:22:28 ... only if i can "borrow" it ... i'll send a moving truck 16:22:33 i swear you'll get it back. 16:22:37 someday 16:22:40 said no one ever 16:23:04 alright - well thanks for coming everyone 16:23:07 i appreciate the time 16:23:21 reminder that we'll have office hours in about 40 minutes 16:23:29 if anyone wants to work on things 16:23:45 #endmeeting