15:00:11 #startmeeting keystone 15:00:11 Meeting started Tue Jan 18 15:00:11 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:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:11 The meeting name has been set to 'keystone' 15:00:18 #topic Roll Call 15:00:21 o/ 15:00:26 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, xek 15:00:35 o/ 15:01:24 o/ 15:01:31 o/ 15:01:42 Great, let's get started 15:01:50 #topic Review Past Meeting Action Items 15:02:13 #link https://meetings.opendev.org/meetings/keystone/2022/keystone.2022-01-11-15.00.html 15:02:17 We didn't have any 15:02:20 Moving on 15:02:47 #topic Liaison Updates 15:02:52 knikolla: around? 15:03:30 o/ 15:03:42 no updates 15:04:10 Cool, thanks 15:04:23 #topic Secure RBAC 15:05:05 Not a whole lot of updates from me this week. We do have some TripleO Heat Template changes pending that need to get merged. I'll probably be harassing the owners this week. 15:05:22 Any questions/comments about SRBAC this week? 15:09:07 OK, moving on ... 15:09:13 #topic OAuth 2.0 15:09:21 h_asahina: around? 15:10:06 yes 15:11:01 Today, I'd like to talk about the necessity of OAuth2.0 Introspection API which I defined in the spec. 15:11:05 Although I defined OAuth2.0 Introspection API in the current spec, maybe it can be omitted. 15:11:44 The purpose of the introspection API is to get metadata and verify the token validity. 15:12:53 As we decided to use X-Auth-Token as OAuth2.0 access token, this purpose can be accomplished through an existing identity API. 15:13:36 So, I think we don't need OAuth2.0 Introspection API. Could you tell me your opinion? 15:14:23 I think we don't need it for now. But it would be a nice thing to have if we want to have more general support for keystone as an authorization server for oauth 2.0. 15:14:44 I agree with that 15:15:32 If we need to support additional token types, we should add it. 15:16:33 Probably more important with new grant types than with token types 15:17:41 Merged openstack/keystone master: sql: Trivial formatting changes https://review.opendev.org/c/openstack/keystone/+/823660 15:18:56 Could you tell me why? I think the situation where we need Introspection API is like when we want to use OAuth2.0 in keystone from the other services from the openstack. 15:20:29 if we add a new grant type, we can use an existing API for the introspection as long as we use X-Auth-Token. Am I wrong? 15:20:39 Services within the OpenStack ecosystem already know how to authenticate to keystone and introspect endpoints (either through the keystoneauth, keystoneclient or keystonemiddleware). 15:20:54 For them an introspection endpoint already exists within the already defined API. 15:21:55 Thus it's services which don't "speak OpenStack" and use OAuth 2.0 entirely, that would require new OAuth 2.0 conforming endpoints and grant types. 15:22:28 The token type is less important, as it's usually treated as opaque. 15:25:24 Is that the situation where we want to use keystone as just an OAuth2.0 authorization server? 15:26:53 Possibly, though it's less about that. It works both ways. If keystone supports open standards, then we can transition other openstack services to talk to keystone using those open standards. Which opens the door for allowing other authorization server to be used in place of keystone if so desired. 15:28:56 You mean by supporting open standard like Introspection API makes the other components like keystonemiddleware to support the standard? 15:29:12 yes 15:29:36 I got it. 15:29:53 However, for now, we don't strongly need it. 15:30:03 Correct 15:30:18 If we implement it, it is just a wrapper of an existing identity API. 15:31:10 Yes. 15:31:20 It's redundant and confusing. So, do you agree with omitting it in Yoga release? 15:31:32 100% 15:31:51 Ok, thanks. I'll update spec. 15:32:08 Cool 15:32:12 Thanks! 15:32:19 Anything else on this topic h_asahina ? 15:32:32 Nothing 15:32:40 OK, moving on 15:32:45 #topic Open Discussion 15:32:52 Any other topics y'all want to talk about? 15:33:03 The CFP for proposals for Berlin is open 15:33:14 Anybody planning to submit anything? Or planning to travel/ 15:33:40 Ah yes, the Summit. 15:33:54 I think it would be good to go talk about the Secure-RBAC work everyone has been doing 15:34:08 I've gotta talk to lbragstad about it. 15:35:57 cool 15:36:27 I have no clue what to propose to talk about yet. 15:38:31 h_asahina you should consider talking about the OAuth work you're doin g. 15:39:16 I don't either 15:40:16 Alright. it's first time for me to attend the Summit, but I'll consider it. 15:42:12 What should I do if I propose something? 15:44:39 hope it gets accepted then speak in front of a crowd :) 15:45:11 h_asahina: The CFP is over here: https://cfp.openinfra.dev/app/berlin-2022 15:45:20 If you do submit something let us know 15:45:39 In the past they've asked folks to vote for the talks that get selected 15:45:51 So I usually ask folks for votes here, haha 15:46:10 thanks. I'll notify here if I submit something. 15:46:36 Cool, any other topics before we take a look at the bugs? 15:46:46 In the past, each project got it's own project update session too. I don't know if that's the case this year as well. 15:47:25 I have two items, the first is with Lance's move this fell through the cracks https://bugs.launchpad.net/keystone/+bug/1901891 so I'll be working on a fix for #3 this week and may ping people for reviews. Second, let me know if you want to be added to the reviewathon invitees, planning on scheduling for this Friday the 21st so please let me know conflicts as well 15:48:46 d34dh0r53: sounds great! 15:48:52 also, my Friday is wide open this week. 15:49:11 excellent knikolla 15:49:27 count me in for Friday as well 15:49:41 thanks dmendiza[m] 15:52:12 We've only got a few minutes left 15:52:21 which is probably not enough for bug triage 15:52:37 So let's punt until next week (or Friday) 15:52:41 Thanks for joining, everyone! 15:52:56 Thanks! 15:52:58 #endmeeting