Thursday, 2018-06-28

*** liuzz has quit IRC00:00
*** alex_xu has joined #openstack-keystone00:04
*** felipemonteiro_ has joined #openstack-keystone00:12
*** itlinux has joined #openstack-keystone00:23
*** felipemonteiro_ has quit IRC00:26
*** gyee has quit IRC00:39
*** Dinesh_Bhor has joined #openstack-keystone01:01
*** spotz has quit IRC01:04
*** itlinux has quit IRC01:08
*** itlinux has joined #openstack-keystone01:12
*** edmondsw has joined #openstack-keystone01:16
*** edmondsw has quit IRC01:20
*** spotz has joined #openstack-keystone01:20
*** raildo has quit IRC01:22
*** gongysh has joined #openstack-keystone01:35
*** liuzz has joined #openstack-keystone01:37
*** liuzz_ has joined #openstack-keystone01:40
*** liuzz has quit IRC01:40
*** AlexeyAbashkin has joined #openstack-keystone02:10
*** links has joined #openstack-keystone02:30
*** links has quit IRC02:30
*** AlexeyAbashkin has quit IRC02:39
*** edmondsw has joined #openstack-keystone03:03
*** tonytan4ever has quit IRC03:07
*** edmondsw has quit IRC03:08
*** tonytan4ever has joined #openstack-keystone03:46
*** tonytan4ever has quit IRC03:50
*** sonuk has joined #openstack-keystone04:07
openstackgerritVishakha Agarwal proposed openstack/keystone master: Added check to avoid keyerror "user['name']"  https://review.openstack.org/57643304:22
*** tonytan4ever has joined #openstack-keystone04:24
*** AlexeyAbashkin has joined #openstack-keystone04:32
*** edmondsw has joined #openstack-keystone04:52
openstackgerritwu.chunyang proposed openstack/python-keystoneclient master: Add release note link in README  https://review.openstack.org/57865204:56
*** edmondsw has quit IRC04:57
*** gongysh has quit IRC05:06
*** AlexeyAbashkin has quit IRC05:25
*** gongysh has joined #openstack-keystone05:31
*** openstackgerrit has quit IRC05:34
*** openstackstatus has quit IRC05:51
*** openstackstatus has joined #openstack-keystone05:52
*** ChanServ sets mode: +v openstackstatus05:52
*** vishakha has quit IRC05:56
*** parthiban has joined #openstack-keystone05:59
*** vishakha has joined #openstack-keystone06:08
parthibanHello all, Can someone help me out on key revocation system to quickly deactivate potentially compromised keys in OpenStack - https://wiki.openstack.org/wiki/Security/Guidelines#key_revocation06:19
*** liuzz_ has quit IRC06:19
*** liuzz has joined #openstack-keystone06:19
*** AlexeyAbashkin has joined #openstack-keystone06:29
*** edmondsw has joined #openstack-keystone06:40
*** AlexeyAbashkin has quit IRC06:41
*** nicolasbock has joined #openstack-keystone06:43
*** edmondsw has quit IRC06:46
*** martinus__ has joined #openstack-keystone06:55
parthibanHello all, Can someone help me out on key revocation system to quickly deactivate potentially compromised keys in OpenStack - https://wiki.openstack.org/wiki/Security/Guidelines#key_revocation07:02
*** peereb has joined #openstack-keystone07:09
*** pcaruana has joined #openstack-keystone07:10
*** tesseract has joined #openstack-keystone07:11
*** amoralej|off is now known as amoralej07:26
*** liuzz_ has joined #openstack-keystone07:37
*** liuzz has quit IRC07:39
*** ispp has joined #openstack-keystone07:54
*** openstackgerrit has joined #openstack-keystone07:55
openstackgerritJuan Antonio Osorio Robles proposed openstack/oslo.policy master: Implement base for pluggable policy drivers  https://review.openstack.org/57780707:55
*** tosky has joined #openstack-keystone07:58
*** threestrands has joined #openstack-keystone08:06
*** d0ugal has joined #openstack-keystone08:08
*** threestrands has quit IRC08:13
*** tonytan4ever_brb has joined #openstack-keystone08:15
*** tonytan4ever has quit IRC08:19
*** tonytan4ever_brb has quit IRC08:20
*** tonytan4ever has joined #openstack-keystone08:20
*** dansmith has quit IRC08:20
*** dansmith has joined #openstack-keystone08:21
*** dansmith is now known as Guest8882308:21
*** edmondsw has joined #openstack-keystone08:29
*** edmondsw has quit IRC08:34
*** d0ugal has quit IRC09:16
*** d0ugal has joined #openstack-keystone09:16
*** pcichy has joined #openstack-keystone09:30
*** Dinesh_Bhor has quit IRC09:34
*** evrardjp has quit IRC09:35
*** pcichy has quit IRC09:35
*** pcichy has joined #openstack-keystone09:35
openstackgerritwu.chunyang proposed openstack/python-keystoneclient master: Add release note link in README  https://review.openstack.org/57865209:38
*** evrardjp has joined #openstack-keystone09:41
*** rcernin has quit IRC09:56
evrardjphello10:02
*** edmondsw has joined #openstack-keystone10:17
*** edmondsw has quit IRC10:22
*** ispp has quit IRC10:25
*** peereb has quit IRC10:43
*** ispp has joined #openstack-keystone10:49
*** gongysh has quit IRC10:52
evrardjpcmurphy: could you help me a little?11:23
evrardjphttps://review.openstack.org/#/c/574414/711:23
evrardjpthat would be great to see this bad boy in :)11:23
cmurphyevrardjp: done11:28
*** sapd_ has joined #openstack-keystone11:33
*** sapd has quit IRC11:33
*** gongysh has joined #openstack-keystone11:36
evrardjpcool thanks11:37
*** pcichy has quit IRC11:43
*** amoralej is now known as amoralej|lunch11:54
*** pcaruana has quit IRC11:56
*** mvk has quit IRC11:56
*** raildo has joined #openstack-keystone12:00
*** edmondsw has joined #openstack-keystone12:06
*** sheel has joined #openstack-keystone12:06
*** edmondsw has quit IRC12:11
parthibanHello all, Can someone help me out on key revocation system to quickly deactivate potentially compromised keys in OpenStack - https://wiki.openstack.org/wiki/Security/Guidelines#key_revocation12:14
jaosoriorlbragstad, hrybacki, cmurphy: Is anything using policy scoping at the moment?12:17
jaosoriorI don't see anywhere in the codebase where the key 'system' for the credentials that are passed to the enforcer would be set. which is what oslo.policy actually checks.12:18
jaosoriorinstead, keystone middleware seems to pass a 'system_scope'12:19
*** vrv_ has joined #openstack-keystone12:26
*** neha_alhat has joined #openstack-keystone12:27
*** mvk has joined #openstack-keystone12:28
cmurphyjaosorior: are you talking about things like this? http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token/_request.py#n6712:28
cmurphyparthiban: keystone isn't a key storage service, what are you actually looking to do?12:29
neha_alhatcmurphy, mordred, kmalloc: can you help me to understand why this job legacy-tempest-dsvm-neutron-src failing on patch: https://review.openstack.org/#/c/578008/12:30
jaosoriorcmurphy: exactly12:31
jaosoriorcmurphy: I don't see that actually being used for policy12:31
cmurphyneha_alhat: http://logs.openstack.org/08/578008/2/check/legacy-tempest-dsvm-neutron-src/0500c4c/logs/screen-g-api.txt.gz?level=ERROR12:32
cmurphyjaosorior: hmm i don't really know, lbragstad will12:35
jaosoriorok12:35
jaosoriorwell for reference, this is what oslo.context will actually output https://github.com/openstack/oslo.context/blob/master/oslo_context/context.py#L32012:36
jaosoriorand this is what oslo.policy will check https://github.com/openstack/oslo.policy/blob/master/oslo_policy/policy.py#L83412:36
jaosoriorlbragstad: ^^12:36
jaosoriorhrybacki: ^^12:37
neha_alhatcmurphy: Thanks, I will fix this12:39
*** pcaruana has joined #openstack-keystone12:44
*** rcernin has joined #openstack-keystone12:52
*** edmondsw has joined #openstack-keystone13:01
*** rcernin has quit IRC13:08
*** amoralej|lunch is now known as amoralej13:14
*** mchlumsky has joined #openstack-keystone13:16
*** mchlumsky has quit IRC13:16
*** mchlumsky has joined #openstack-keystone13:18
lbragstadparthiban: the looks like the OpenStack security wiki, which keystone doesn't maintain directly. it might be worth checking with the openstack-security team directly13:38
lbragstadjaosorior: system scope should be working for things that specify it13:40
lbragstadwith scope_typse13:40
lbragstadjaosorior: last i checked, at least in the keystone code, the creds dictionary gets populated based on the token13:54
openstackgerritStephen Finucane proposed openstack/keystone master: Replace support matrix ext with common library  https://review.openstack.org/52780813:55
*** Guest88823 is now known as dansmith14:01
openstackgerritLance Bragstad proposed openstack/keystone master: Remove KeystoneToken object  https://review.openstack.org/57756714:01
openstackgerritColleen Murphy proposed openstack/keystone master: Add new "How Can I Help?" contributor guide  https://review.openstack.org/57881414:09
*** lbragstad has quit IRC14:10
*** ispp has quit IRC14:14
kmallocjaosorior: the token is mostly what populates the creds dict. It is just the auth_context dict.14:19
*** itlinux has quit IRC14:26
*** lbragstad has joined #openstack-keystone14:38
*** ChanServ sets mode: +o lbragstad14:38
knikollalarsks: https://review.openstack.org/#/c/52991414:42
knikollathis is in queens14:43
larsksknikolla: yes, I was already looking at that :)14:43
knikollaawesome14:43
knikollalarsks: i changed the bug to incomplete, after trying that out report back and i'll set it to invalid if everything works fine.14:44
larsksWill do. I'll try to patch that into our environment this afternoon.14:44
jaosoriorkmalloc, lbragstad: Alright, I was just reading the code and didn't understand where that was happening. Where is that set?14:46
lbragstadso - when keystone processes a request14:48
lbragstadwe override the call to keystone in keystonemiddleware, because that wouldn't make sense, right?14:48
jaosoriorright14:50
lbragstadjaosorior: instead we just load the token provider api directly14:50
lbragstadand ask it to validate14:50
lbragstadhttps://git.openstack.org/cgit/openstack/keystone/tree/keystone/middleware/auth.py#n4714:50
jaosoriorok, that makes sense14:50
lbragstadso - the contents of ^ get set in the context, yeah?14:50
jaosorioruhm14:50
jaosoriorsure, I guess14:50
lbragstads/, yeah?//14:50
lbragstadsorry14:50
jaosoriorbut you still have the context14:50
jaosoriorwhich is what actually populates the creds (from what I could see from the code)14:51
openstackgerritMatthew Thode proposed openstack/keystone master: pycrypto is not used by keystone  https://review.openstack.org/57883314:51
lbragstadyeah - so it gets put into the require environment14:51
lbragstadrequest environment&14:51
jaosorioryes14:52
lbragstadwe pull that token out of that environment later on, which ends up building the creds dictionary which is passed to oslo.policy14:52
jaosoriorthat's the bit I'm missing14:52
lbragstad(kmalloc and i were both just digging around in this code)14:52
lbragstadit's crazy confusing right now :( at least IMO14:53
jaosoriorit sure is :D14:53
lbragstadhttps://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/authorization.py#n13414:53
lbragstad^ that is suppose to get called if you wrap a methed with @controller.protected14:53
jaosoriorsure14:53
jaosorior_build_policy_check_credentials basically is just a call to get AUTH_CONTEXT_ENV14:54
lbragstadwhich should call this https://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/authorization.py#n6414:54
lbragstadyep14:54
jaosoriorbut that one (as far as I can tell) gets populated with the context14:54
jaosoriornot with the token14:54
lbragstad:)14:55
kmallocThe token is in the context, and the context is based upon the token.14:55
jaosoriorkmalloc: right14:55
kmallocAnd not the subject token.14:55
lbragstadjaosorior: it's this bit https://git.openstack.org/cgit/openstack/keystone/tree/keystone/middleware/auth.py#n21914:56
kmallocThat is in the target dict (and limited values of it)14:56
lbragstad^ which really threw me off14:56
lbragstadkeystone validate the token based on the ID14:56
lbragstadand technically gets back this token response, which is a dictionary14:56
lbragstadthen it gets passed to the KeystoneTOken object...14:56
lbragstadwhich is a dict type object https://git.openstack.org/cgit/openstack/keystone/tree/keystone/models/token_model.py#n3414:57
jaosoriorright, but I'm talking about creds, not the target dict14:57
lbragstadthe creds contain that dictionary...14:57
jaosoriorcreds gets filled out from AUTH_CONTEXT.14:57
lbragstadwhich gets recursively parsed in oslo.policy14:57
jaosoriorwhich gets filled out in that code... here https://git.openstack.org/cgit/openstack/keystone/tree/keystone/middleware/auth.py#n22314:57
jaosoriorwhich is the context's result of the to_policy_values function14:58
*** alex_xu has quit IRC14:58
lbragstadand on https://git.openstack.org/cgit/openstack/keystone/tree/keystone/middleware/auth.py#n23314:58
lbragstadwe are amending the auth_context with a token variable, which is an instance of KeystoneToken14:58
jaosoriorlbragstad: right, but that's just an update in case there are trust-related things to add14:59
lbragstadthe token is always added though14:59
jaosoriorsure14:59
lbragstadthe trust values can be None14:59
*** gongysh has quit IRC15:00
jaosorioralright, so we have the token there; sorry to be dense, but I still don't see where the system scope is added to the creds dictionary15:00
jaosoriorthere is a "system_scope" entry... which is not used at all in oslo.policy15:00
jaosorioroslo.policy itself expects a "system" entry in the creds dict, which is what I still don't know where it gets filled out15:00
*** alex_xu has joined #openstack-keystone15:00
lbragstadso - you have auth_context['token'] right?15:01
lbragstadand it's an instance of KeystoneToken15:01
jaosoriorI guess "D15:01
jaosorior:D15:01
lbragstadif you call auth_context['token']['system'] you get the system scope of the token, if it is system-scoped15:01
jaosoriorOK15:01
lbragstadthe KeystoneToken object uses reflection to model whatever dictionary is passed into it15:02
lbragstadand since it is of type dict, using oslo.policy token.get('system') on it works15:02
lbragstad=/15:02
jaosoriorlbragstad: but it's not token.get('system')15:02
jaosoriorit's creds.get('system')15:02
jaosoriorwe don't get the token from the creds (which is what would have worked)15:03
jaosoriorsorry to be dense here, maybe I'm still not understanding something15:03
lbragstadhttps://github.com/openstack/oslo.policy/blob/master/oslo_policy/_checks.py#L30215:03
lbragstadbecause we hit this in oslo.policy ^15:03
jaosoriorlbragstad: uhm... but, policy isn't converted into an oslo policy Check object, it's a dict directly https://github.com/openstack/oslo.policy/blob/master/oslo_policy/policy.py#L83415:05
lbragstadthat code processes before we get to taht line https://github.com/openstack/oslo.policy/blob/master/oslo_policy/policy.py#L81415:05
lbragstadwait - nevermind15:06
lbragstadso - taking a step back15:06
lbragstadhttps://git.openstack.org/cgit/openstack/keystone/tree/keystone/middleware/auth.py#n24815:06
jaosoriorright15:06
lbragstad^ at that point we know auth_context['token'] is an instance of KeystoneToken15:07
jaosorioryes15:07
lbragstadand we see that we're setting it on the request environment of the request15:07
jaosorioryep15:07
lbragstadlater on - we see that we're pulling out that auth_context in authorization.py15:07
lbragstadhttps://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/authorization.py#n6415:07
lbragstadand that is populating the creds dictionary15:08
jaosorioryeah15:08
lbragstadso - creds == auth_context, right?15:08
jaosoriorcorrect15:08
* lbragstad is grabbing a trace15:10
*** itlinux has joined #openstack-keystone15:11
*** mvenesio has joined #openstack-keystone15:14
lbragstadjaosorior: you're right15:19
lbragstadwe're missing a patch that I thought had merged15:20
lbragstadhttps://review.openstack.org/#/c/551336/115:20
lbragstadit looks like https://review.openstack.org/#/c/551336/1/keystone/middleware/auth.py@170 would do it15:20
jaosoriorah!! now that makes sense! :D15:20
lbragstadwho knew it'd be easier to put puzzles together with *all* the pieces15:21
jaosoriorhah :D15:21
lbragstadi apologize...15:21
lbragstadi was convinced all that had been ironed out..15:21
lbragstadthat makes sense because i needed to have that in order to start doing https://review.openstack.org/#/c/551337/315:22
*** mchlumsky has quit IRC15:23
jaosoriorlbragstad: so yeah, NOW it makes sense to me :D15:24
lbragstadme too15:24
jaosoriorthanks for taking the time to look at it15:24
lbragstadyeah, thanks for asking the hard questions15:24
*** gyee has joined #openstack-keystone15:24
lbragstadnow that we both know way more about keystone enforcement path than we'd like...15:24
lbragstaddo you think that is the way we should be going about it?15:25
jaosoriorlbragstad: I actually am not very keen on having a "system" key in creds15:25
lbragstadyeah - me either...15:25
jaosoriorI think it would be nicer to always have a "token_scope" key15:25
jaosoriorthat defaults to "project"15:26
jaosoriorand set "system" there, when it's a system scoped call15:26
lbragstadi would like for https://review.openstack.org/#/c/551336/1 to not be required...15:26
jaosoriorI can surely work with what's there now, no biggie :D. But it would be nice to have something else15:26
lbragstadso - for example15:26
lbragstadkeystonemiddleware sits in front of us, and other services right?15:27
jaosorioryes15:27
lbragstadit does the whole validate token thing15:27
lbragstadand populates the context15:27
lbragstadand sets all that in the request environment for us15:27
jaosoriorIMO this should be logic that's in oslo.context. Since we do get the token there, we could parse it for the needed values, and output it appropriately15:27
jaosoriorthat way that change propagates for all the projects.15:28
lbragstad++15:28
lbragstadrigyht15:28
lbragstadi think creds is kind of opaque15:28
jaosoriorit sure is15:28
lbragstads/kind of//15:28
lbragstadinstead, what if we just pass oslo_policy enforce an instance of the context object15:28
jaosorioranother option is, if you want to work with what's there already, we could check for system_scope from creds in oslo.policy15:29
lbragstadsure - we could support both ways15:29
lbragstadif services are setting creds.system_scope we'll validate that way15:29
lbragstadotherwise we can accept an instance of oslo.context15:29
jaosoriorlbragstad: currently services are passing the bare minimum they can to creds15:29
lbragstadright15:29
lbragstadoslo.context already understands system_scope https://github.com/openstack/oslo.context/blob/master/oslo_context/context.py#L5215:30
lbragstadhttps://github.com/openstack/oslo.context/commit/1a40b3d43bac5244bcba6bdbc4802fb76430d8d315:30
jaosorioryes15:30
jaosoriorand it's getting populated appropriately (at least in keystone)15:30
lbragstadand as long as they are building the context using from_environ()15:30
jaosoriormost services are doing that15:30
jaosoriornot sure if all15:30
lbragstadwe'll likely have a sane object to parse in oslo.policy15:30
lbragstadi know nova uses oslo.context heavily15:30
lbragstadand builds it from environ iirc15:31
jaosoriornova's doing that15:31
jaosoriorneutron too15:31
lbragstadnice15:31
*** sonuk_ has joined #openstack-keystone15:31
lbragstadbut - if we convert them to using oslo.context for this type of stuff, then it should be more consistent for us to rely on in oslo.policy15:31
jaosoriorlbragstad:  that would be a nice goal15:32
lbragstadversus handling a bunch of different snowflakes that is the current creds dictionary15:32
jaosoriorand it makes sense, since everybody's using oslo.context15:32
lbragstadright15:32
lbragstadso - what would we need to do to make this happen?15:33
lbragstadksm already validates the token and sets headers15:33
jaosoriorlbragstad: if you want me to do it... for me to get back from vacations :D (last day today before that)15:33
jaosoriorelse15:33
jaosoriorwe would need to modify the Enforcer's enforce function (from oslo.policy) to check creds15:34
lbragstadyeah - i suppose we'd need to teach oslo.policy how to deal with oslo.context objects15:34
jaosoriorif creds is an oslo.context object, we could call to_dict (or to_policy_values), and get creds to be that15:34
*** mvenesio has quit IRC15:35
jaosoriorthat would assure that we need to make the least changes15:35
lbragstadyeah15:35
kmalloclbragstad: well.. a.flattened oslo.context15:35
*** sonuk has quit IRC15:35
kmallocI would keep the policy engine to natives, even if it just does a to_dict if it sees a oslo.context obkext.15:35
lbragstadthat makes sense15:36
lbragstadthat's going to allow services to keep doing what they do today, which is fine15:36
kmallocYep.15:36
lbragstadbut it gives the flexibility to pass in oslo.context objects instead15:36
lbragstadwhich is a nice carrot15:36
kmallocAnd keeps the engine as dumb as possible.15:36
jaosorioryeah, so, a call to to_dict or to_policy_values, is the way to go. Shouldn't be too big of a change :D15:37
lbragstadbecause it allows services to use the interactions between ksm and oslo.context to populate scope15:37
kmallocAlso, creds in keystoen's case isn't just oslo_context.15:37
kmallocJust fyi15:37
*** fiddletwix has quit IRC15:37
jaosoriorit isn't?15:37
kmallocNo, auth_context is different15:37
lbragstadit's a mess of stuff...15:37
*** fiddletwix has joined #openstack-keystone15:37
jaosoriorkmalloc: you're right15:37
jaosoriorit's a convination of to_policy_values and trust-related things15:38
jaosoriorthe plot thickens :D15:38
kmallocI just rewrote the enforcement in keystone to something better15:38
lbragstadhttp://paste.openstack.org/raw/724535/15:38
kmallocSo it wasn't @protected15:38
jaosorioroh yeah, I was looking at that patch15:38
lbragstadjaosorior: since you know all of this, your eyes on that patch would be awesome ;)15:38
lbragstadpatch series15:39
jaosoriorsure :D15:39
jaosoriorI can check it out in three weeks15:39
jaosorioryou really don't want me to review your code while I'm drunk in Mexico15:39
kmallocIt might be useful for you, it has better docs what each thing passed to enforcer is15:39
lbragstadjaosorior: don't we though?15:39
kmallocRegardless if you review it.15:39
*** ispp has joined #openstack-keystone15:40
kmallocAnd has tests you can look at to see the data structures.15:40
kmalloc;)15:40
kmallocDrunk code review, that is the new sport, right? ;)15:40
kmallocComing to the Olympic Games near you!15:40
lbragstadlol15:40
lbragstadso - walking through this again15:41
lbragstadbut all services would need to do would be to build context objects using oslo.context's from_environ() method15:41
jaosorioryes15:41
lbragstadsince that knows to look for different scopes set by ksm15:41
lbragstadand sets them appropriately on the context object15:42
lbragstadthen the service just passes it to oslo.policy in enforce15:42
lbragstadand oslo.policy learns to deal with oslo.context objects15:42
lbragstad(which is a better interface than a random dictionary, IMO)15:42
jaosoriorthat sounds like a plan15:43
lbragstadsweet15:43
lbragstadsince the real piece of work is in oslo.policy15:43
lbragstadshould we just keep this isolated to an RFE there?15:43
jaosorioryeah15:43
lbragstadthere isn't any keystone, ksm, or oslo.context work to do, is there?15:43
lbragstadat least not from what i can tell15:44
jaosoriorthere isn't (at this moment)15:44
jaosoriorMAYBE for oslo.context15:44
lbragstadcool15:44
jaosoriorif we want to pass more specific info15:44
lbragstadright - at which point, we'll add to oslo.context and release15:44
lbragstadthen consume it in oslo.policy15:44
jaosoriorright15:44
*** mchlumsky has joined #openstack-keystone15:44
jaosoriortalking about oslo.policy15:44
jaosoriorhrybacki mentioned it to you the other day, but I'm doing some work on getting oslo.policy to be pluggable15:45
jaosoriorwould really apprecite your reviews here https://review.openstack.org/#/q/topic:bp/pluggable-policy-drivers+status:open15:45
jaosoriorseems to be working :D15:45
lbragstadah - that's right15:45
jaosorior(that's how I started looking at all of this in the first place)15:45
lbragstadis oslo in spec freeze?15:45
jaosoriorno idea15:45
jaosoriorI submitted it for stein anyways15:46
jaosoriorbut if it can merge this release15:46
jaosoriorit would be better :D15:46
lbragstadoh - nice15:46
lbragstadyeah - i can take a look at this15:46
*** parthiban has quit IRC15:46
lbragstadi'll get an oslo.policy bug opened describing the RFE15:46
jaosoriorSo... as I mentioned, I'll be gone 3 weeks. So, if you, or hrybacki, or someone can take over that work while I'm gone (in case it needs some small changes) it would be awesome15:47
lbragstadthsi work https://review.openstack.org/#/q/topic:bp/pluggable-policy-drivers+(status:open+OR+status:merged) ?15:47
jaosoriorlbragstad: just asked bnemec, feature freeze is next week15:47
jaosoriorlbragstad: yeah15:47
lbragstadack15:48
jaosoriorthanks15:48
lbragstadthank you15:48
*** sheel has quit IRC15:55
*** amoralej is now known as amoralej|off16:02
lbragstadjaosorior: kmalloc hrybacki https://bugs.launchpad.net/oslo.policy/+bug/177917216:10
openstackLaunchpad bug 1779172 in oslo.policy "RFE: policy enforcement should accept context objects" [Undecided,New]16:10
*** d0ugal has quit IRC16:17
jaosoriorlbragstad++16:19
*** ispp has quit IRC16:20
*** raopajay has quit IRC16:26
*** tesseract has quit IRC16:38
*** jmlowe has quit IRC16:41
*** vrv_ has quit IRC16:55
*** jmlowe has joined #openstack-keystone16:56
*** jaosorior has quit IRC17:10
*** raildo has quit IRC17:12
cmurphykmalloc: re https://review.openstack.org/#/c/576660/ remind me why we added a new password_hash column instead of just doing an alter column to increase the varchar size?17:26
kmallocNo downtime upgrades.17:27
cmurphyan alter column causes downtime?17:27
kmallocAlter locks tables17:27
kmallocSo it has to be in contract phase.17:27
kmallocWell alter in some forms17:27
kmallocChanging a column def does.17:27
kmallocAdding a column does not.17:28
kmallocReally, it was a lot of headache :(, I would have preferred a straight alter and increase the varchar.17:29
cmurphyyeah it seems like a ton of hassle :(17:33
kmallocWell, the other reason. Was because old keystoen's couldn't read bcrypt/scrypr17:34
kmallocSo we had to have a way to write old password (sha256)17:34
*** tonytan4ever_brb has joined #openstack-keystone17:34
kmallocFor rolling upgrades17:34
cmurphyoh i see17:35
cmurphythat makes a little more sense17:35
kmallocI could have backported a patch to decode bcrypt/scrypt17:35
*** mvk has quit IRC17:35
cmurphythat would have violated stable policy i think17:35
kmallocBut both things made it just eaiser to do a new column.17:35
kmallocNot if it didn't involve a new lib17:35
cmurphyit would have been adding a new feature17:36
kmallocI could have done it in pure Python and it wouldn't have allowed new password hashing for storage.17:36
kmallocJust "if you see bcrypt, do x"17:36
kmallocNot really a feature, just data processing.17:36
*** tonytan4ever has quit IRC17:37
kmallocSince old keystone's couldn't be told to store passwords in bcrypt. That said. We didn't fight that battle17:37
kmallocWe went this way.17:37
kmallocAnd in Stien, I'll drop the old column :)17:37
*** jmlowe has quit IRC17:46
*** raildo has joined #openstack-keystone18:05
*** jmlowe has joined #openstack-keystone18:08
larsksknikolla: that patch sort of solves the problem, but it appear to break the client here: https://github.com/openstack/osc-lib/blob/master/osc_lib/utils/__init__.py#L26718:11
larsksThe osc_lib code is calling resource.get('id') here, but it really wants resource.id.  `get` appears to do something different.18:11
larsksknikolla: http://termbin.com/r77e18:12
*** pcaruana has quit IRC18:14
*** pooja-jadhav has joined #openstack-keystone18:44
*** bhagyashri_s has joined #openstack-keystone18:44
*** bhagyashris has quit IRC18:47
*** pooja_jadhav has quit IRC18:47
*** pooja_jadhav has joined #openstack-keystone18:51
*** neha_alhat has quit IRC18:52
*** bhagyashris_ has joined #openstack-keystone18:52
*** pooja-jadhav has quit IRC18:54
*** bhagyashri_s has quit IRC18:54
*** tonytan4ever_brb has quit IRC18:56
*** tonytan4ever has joined #openstack-keystone18:56
*** mvenesio has joined #openstack-keystone19:17
*** itlinux has quit IRC19:29
*** itlinux has joined #openstack-keystone19:31
knikollalarsks: did u try with the latest openstackclient from pip?20:17
larsksknikolla: No, because we're running pike and I was hoping the backport would Just Work.20:17
knikollalarsks: openstackclient should work regardless of server version20:17
larsksThat broke basically everything everywhere (because everything uses that library), so I'm probably not going to pursue it at this point.20:18
knikollavirtualenv?20:18
knikollafrom your pc?20:18
larsksWhen I modified the existing file to use .id instead of .get('id'), it was able to look up a federated user by name.20:18
larsksSure, I can test it from a virtualenv, but we're not going to be able to run the patch on the servers in any case because it would require updated osc_lib everywhere, which has support implications.20:19
*** itlinux has quit IRC20:28
*** tonytan4ever_brb has joined #openstack-keystone20:37
*** d0ugal has joined #openstack-keystone20:38
*** tonytan4ever has quit IRC20:39
openstackgerritLance Bragstad proposed openstack/oslo.policy master: Pass dictionary as creds in policy tests  https://review.openstack.org/57899420:40
openstackgerritLance Bragstad proposed openstack/oslo.policy master: Teach Enforcer.enforce to deal with context objects  https://review.openstack.org/57899520:40
*** martinus__ has quit IRC20:40
lbragstadkmalloc: ^ per our discussion with jaosorior20:40
*** itlinux has joined #openstack-keystone20:42
*** raildo has quit IRC20:44
*** mvk has joined #openstack-keystone20:47
*** raildo has joined #openstack-keystone20:50
*** d0ugal has quit IRC20:57
openstackgerritRaildo Mascena proposed openstack/keystone master: Exposing ambiguity bug when querying role assignments  https://review.openstack.org/57043820:57
openstackgerritRaildo Mascena proposed openstack/keystone master: Exposing ambiguity bug when querying role assignments  https://review.openstack.org/57043821:10
openstackgerritLance Bragstad proposed openstack/oslo.policy master: Teach Enforcer.enforce to deal with context objects  https://review.openstack.org/57899521:13
*** edmondsw has quit IRC21:31
*** raildo has quit IRC21:40
*** rcernin has joined #openstack-keystone21:42
*** mchlumsky has quit IRC21:42
*** mchlumsky has joined #openstack-keystone21:43
*** mvenesio has quit IRC21:45
*** itlinux has quit IRC21:50
*** raildo has joined #openstack-keystone21:55
*** mchlumsky has quit IRC22:00
lbragstadwxy: https://review.openstack.org/#/q/status:open+project:openstack/python-openstackclient+branch:master+topic:bp/unified-limits should be fixed up and passing now22:12
*** nicolasbock has quit IRC22:14
*** linkmark has quit IRC22:38
*** tosky has quit IRC22:53
*** tonytan4ever_brb has quit IRC23:03
*** tonytan4ever has joined #openstack-keystone23:03
*** threestrands has joined #openstack-keystone23:05
*** threestrands has quit IRC23:05
*** threestrands has joined #openstack-keystone23:05
kmalloclbragstad: nice.23:14
*** threestrands has quit IRC23:38
*** masber has quit IRC23:48
*** gagehugo has quit IRC23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!