15:26:29 #startmeeting Keystone 15:26:29 Meeting started Tue May 3 15:26:29 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:26:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:26:29 The meeting name has been set to 'keystone' 15:26:39 #topic Roll Call 15:26:57 Courtesy ping for admiyo, bbobrov, crisloma, d34dh0r53, dpar, dstanek, hrybacki, knikolla, lbragstad, lwanderley, kmalloc, rodrigods, samueldmq, ruan_he, wxy, sonuk, vishakha, Ajay, rafaelwe 15:27:21 As usual the agenda is over here: 15:27:22 #link https://etherpad.opendev.org/p/keystone-weekly-meeting 15:28:10 o/ 15:29:53 o/ 15:30:33 OK, let's get started 15:30:42 #topic Review Past Meeting Action Items 15:30:45 #link https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-04-26-15.02.html 15:30:48 Looks like we didn't have any 15:31:04 #topic Liaison Updates 15:31:12 I don't have any updates this week. 15:33:22 #topic OAuth 2.0 15:33:36 We had a review session last week 15:34:43 #link https://review.opendev.org/q/topic:bp%252Foauth2-client-credentials-ext 15:34:57 I don't think we have any updates for today 15:39:21 moving on ... 15:39:29 #topic Secure RBAC 15:39:54 In case you missed the Google Meet session, we did discuss the "service" role a bit 15:40:05 We'll continue discussions next week. 15:40:22 #topic Guidance for storing user tokens 15:40:40 dansmith asked this in the channel a while back (sorry we didn't get to it last week) 15:41:18 He's basically looking for guidance in handling user tokens. 15:41:30 IIRC, they're wanting to log them or store them in the DB 15:41:41 presumable to be reused again, during long-running tasks. 15:41:47 *presumably 15:43:07 Hmmm, interesting 15:43:39 My initial gut reaction is no 15:45:38 But I can see the need for it 15:47:35 Can we set an expiry on issued tokens? 15:49:04 That’s the way it aready is. Configurable but defaults to 45 mins I think 15:49:18 d34dh0r53: yeah, tokens expire, but some services can still use them for context when doing long running tasks 15:49:27 but not overrideable during the issue? 15:50:19 No, you can’t ask for a longer living token than the config 15:51:11 No, you can’t ask for a longer living token than the config 15:51:28 hmm, ack 15:52:47 We may need to think about it for a bit 15:53:14 but it would be good to have an opinion on best practices for what to do with the tokens 15:53:50 Agree, i can spend some time thinking about this 15:54:47 dmendiza[m]: to be clear, I want to neither store nor log them 15:54:59 I just want there to be some guidance about that being a bad idea that I can point to whilst arguing :P 15:55:12 :) 15:56:38 That’s easier :) 15:57:17 ack, I missed that last time, haha 15:57:18 Store tokens, bad. You can link to this irc log, haha. 15:59:32 knikolla: ack, I'll take it as better than nothing, but.. seems like it might be good to capture some of those sorts of recommendation somewhere.. I know, easy for me to say 16:00:09 I’m sure there’s something in the docs and if not I’ll put it there 16:00:46 OK, we're just about out of time. 16:00:51 No bug review this week. 16:01:04 We'll get back to normal once the Secure RBAC sessions start winding down. 16:01:15 Thanks for joining, everyone! 16:01:18 #endmeeting