Tuesday, 2018-09-25

*** zigo has quit IRC00:05
*** mvkr has quit IRC00:27
*** mvkr has joined #openstack-keystone00:38
*** aning_ has joined #openstack-keystone01:01
*** aning has quit IRC01:04
*** aning has joined #openstack-keystone01:05
*** aning_ has quit IRC01:07
*** aning_ has joined #openstack-keystone01:08
*** aning has quit IRC01:11
*** aning has joined #openstack-keystone01:11
*** aning_ has quit IRC01:13
*** Dinesh_Bhor has joined #openstack-keystone01:41
*** Dinesh_Bhor has quit IRC01:41
*** felipemonteiro has joined #openstack-keystone02:01
*** felipemonteiro has quit IRC02:02
adriantlbragstad, kmalloc, gagehugo: I'm reading through release notes again and came across the fact that we allow a user to change their password without first getting token now if they know the original password. We haven't I don't think added any MFA support on top of that.02:13
adriantBecause right now you can lock someone out of their account if you know their password, but not their totp code.02:14
kmallocWe always allowed password change without token.02:17
adriantOh, but with that change we also allowed it for expired ones?02:17
kmallocCorrect02:18
adriantkmalloc: should we consider adding MFA based protections on top of that?02:18
kmallocUnsure.02:18
kmallocMaybe. Let's get the auth receipts first.02:19
adriantoh yeah02:19
kmallocWe can enhance other APIs independently02:19
adriantthis would be follow up02:19
adriantwe're just finally doing a keystone upgrade and this is giving me a good reason to read through all the release notes as I go02:19
adriantand thought I'd ask about this02:20
adriantkmalloc: https://review.openstack.org/#/c/404022 but this change dropped the @controller.protected() decorator, i thought that (until that patch) meant it needed a token?02:24
adriantso only in Ocata did we allow a no token method to change password?02:24
kmallocadriant: v2 vs. v3.02:25
kmallocIt was always intended for no token. So maybe in ocata.02:26
adriantOh so v2 always let you do it without token, but only in Ocata did we make v3 let you? Maybe?02:27
kmallocPossibly02:27
kmallocRelated to pci-dss.02:27
gagehugoyeah pci-dss related02:28
kmallocBut needing a token breaks the self-service password change functionality02:28
*** felipemonteiro has joined #openstack-keystone02:28
*** dave-mccowan has quit IRC02:29
adriantbut no sensible system with MFA support would let you change password if you don't meet all the other auth requirements, so we may need to consider a middle ground were you can supply an auth receipt and the old expired password02:30
adriantor something potentially less silly :/02:30
adriantI assumed this was mostly in the context of expired passwords, because surely if your password isn't expired you can always get a token02:31
adriantyeah, before that patch the API was protected, and then eventually we remembered to remove the policy: https://github.com/openstack/keystone/commit/77bf1ad0b8991abb6c7ebba608fde27a3fd01c0902:37
*** sapd1_ has quit IRC02:37
*** sapd1 has joined #openstack-keystone02:39
*** felipemonteiro has quit IRC02:43
*** imacdonn has quit IRC02:50
*** imacdonn has joined #openstack-keystone02:50
*** felipemonteiro has joined #openstack-keystone03:11
*** felipemonteiro has quit IRC03:30
*** Dinesh_Bhor has joined #openstack-keystone03:46
*** Dinesh_Bhor has quit IRC03:48
*** Dinesh_Bhor has joined #openstack-keystone03:49
*** Dinesh_Bhor has quit IRC04:01
*** rcernin has quit IRC04:24
*** Dinesh_Bhor has joined #openstack-keystone04:34
*** rcernin has joined #openstack-keystone04:37
*** Dinesh_Bhor has quit IRC05:00
*** Dinesh_Bhor has joined #openstack-keystone05:08
*** shyamb has joined #openstack-keystone05:14
openstackgerritVishakha Agarwal proposed openstack/keystone master: Purge soft-deleted trusts  https://review.openstack.org/60497005:16
*** rcernin_ has joined #openstack-keystone05:17
*** lbragstad has quit IRC05:18
*** lbragstad has joined #openstack-keystone05:18
*** ChanServ sets mode: +o lbragstad05:18
*** rcernin has quit IRC05:19
*** jaosorior has joined #openstack-keystone05:20
*** shyamb has quit IRC05:26
*** shyamb has joined #openstack-keystone05:31
*** pcaruana has joined #openstack-keystone05:41
*** belmoreira has joined #openstack-keystone05:59
*** shyamb has quit IRC06:05
*** shyamb has joined #openstack-keystone06:09
*** shyamb has quit IRC06:12
*** shyamb has joined #openstack-keystone06:13
openstackgerritVishakha Agarwal proposed openstack/keystone master: Purge soft-deleted trusts  https://review.openstack.org/60497006:34
*** shyamb has quit IRC06:50
openstackgerritVishakha Agarwal proposed openstack/keystone master: Adding test case for MappingEngineTester  https://review.openstack.org/60353906:54
openstackgerritMerged openstack/keystoneauth master: Cache root urls with and without trailing slashes  https://review.openstack.org/60463507:03
*** shyamb has joined #openstack-keystone07:04
*** rcernin_ has quit IRC07:05
*** Dinesh_Bhor has quit IRC07:07
*** mattgo has joined #openstack-keystone07:28
*** shyamb has quit IRC07:32
*** Dinesh_Bhor has joined #openstack-keystone07:36
*** shyamb has joined #openstack-keystone07:45
*** shyamb has quit IRC07:56
*** Dinesh_Bhor has quit IRC08:28
*** Dinesh_Bhor has joined #openstack-keystone08:53
*** shyamb has joined #openstack-keystone08:53
*** Emine has joined #openstack-keystone09:18
openstackgerritColleen Murphy proposed openstack/keystone master: Convert legacy functional jobs to Zuul-v3-native  https://review.openstack.org/60245209:19
openstackgerritVishakha Agarwal proposed openstack/python-keystoneclient master: create() call in v3.regions.py is wrong  https://review.openstack.org/59492109:27
*** vishakha has joined #openstack-keystone09:37
*** shyamb has quit IRC09:38
*** shyamb has joined #openstack-keystone10:29
*** rcernin_ has joined #openstack-keystone10:43
*** rcernin_ has quit IRC10:52
*** Dinesh_Bhor has quit IRC10:56
*** shyamb has quit IRC11:12
*** pcaruana has quit IRC11:15
openstackgerritMonty Taylor proposed openstack/keystoneauth master: Reformat Adapter docstring  https://review.openstack.org/60504211:24
openstackgerritMonty Taylor proposed openstack/keystoneauth master: Add support for client-side rate limiting  https://review.openstack.org/60504311:24
mordredcmurphy, kmalloc, adriant: ^^ I **clearly** need to add tests for that, but I believe that will let us remove the TaskManager from openstacksdk and nodepool and expose the fancy extra goodness we've been doing there to all of the consumers11:25
cmurphymordred: that sounds exciting11:29
mordredcmurphy: yah - I'm pretty pleased so far - it only required writing one class that should be in the standard library11:30
mordredbut otherwise is shockingly straightforward- unless I'm *completely* missing a logic11:30
* cmurphy looks at it11:31
cmurphyoh, adding thread locking to a requests lib, totally straightforward11:32
mordredyah. now - writing the unit tests for it, on the other hand...11:33
mordredwill probably take the rest of the week11:33
cmurphymordred: are you sure this belongs in ksa and not back in openstacksdk?11:34
mordredcmurphy: I've got a patch for it for openstacksdk too ... so it can live either place - but I figured I'd float it over here to see what people think11:35
*** mattgo has quit IRC11:35
mordredcmurphy: https://review.openstack.org/#/c/604926 fwiw11:36
cmurphyi have a little bit of hesitation about this feature creep11:37
cmurphyinterested in how kmalloc feels11:37
mordredyah - and totally fair11:37
mordredI'm good either way - kinda whatever folks think11:37
mordredthere isn't an explicit need for it to be down in ksa like there was for discovery stuff11:38
kmalloccmurphy: I am perfectly fine with this in KSA if it can be encapsulated nicely11:41
kmallocIneed to look at the code and see how it fits, but it isn't outside of something I see as valuable.11:41
kmallocI also might look and say "yeah, this is sdk clearly"11:42
kmallocSo, ... Let me look at the code today :)11:43
kmalloc(will be not pre-5am insomnia code review though)11:43
cmurphykmalloc: i was wondering why you and mordred appeared at the same time11:44
kmallocHave been awake for 4 hours11:45
cmurphy:O11:46
kmallocLot on my mind and busy couple days this week11:46
*** shyamb has joined #openstack-keystone11:48
mordredkmalloc: I haven't been up for 4 hours - but I have been up for 3 - because NO REASON11:57
kmallocStupid no reason no sleep ;)11:58
* kmalloc shakes fist at no reason. 11:58
mordredkmalloc: no reason is the worst isn't it?11:59
kmallocTotally.12:00
*** aojea has joined #openstack-keystone12:00
kmallocMakes for less than fun following days12:00
kmallocOften... Sleepy, moderately unproductive12:00
*** mattgo has joined #openstack-keystone12:02
*** raildo has joined #openstack-keystone12:12
*** shyamb has quit IRC12:31
*** lbragstad has quit IRC12:47
*** aojea has quit IRC12:51
*** lbragstad has joined #openstack-keystone12:59
*** ChanServ sets mode: +o lbragstad12:59
*** belmoreira has quit IRC13:05
*** lbragstad has quit IRC13:09
*** lbragstad has joined #openstack-keystone13:23
*** ChanServ sets mode: +o lbragstad13:23
*** lbragstad has quit IRC13:24
*** lbragstad has joined #openstack-keystone13:24
*** ChanServ sets mode: +o lbragstad13:24
*** aojea has joined #openstack-keystone13:26
*** lbragstad has quit IRC13:26
*** lbragstad_ has joined #openstack-keystone13:26
*** ChanServ sets mode: +o lbragstad_13:26
*** lbragstad_ has quit IRC13:26
*** lbragstad has joined #openstack-keystone13:27
*** ChanServ sets mode: +o lbragstad13:27
*** belmoreira has joined #openstack-keystone13:29
*** aojea has quit IRC13:30
*** wxy| has joined #openstack-keystone13:45
*** wxy| has quit IRC13:49
cmurphyhrybacki: mind sending me an invite re the stein board? i would be a bit late but i'd like to join if possible14:49
*** wxy-xiyuan has quit IRC14:50
hrybackicmurphy: https://trello.com/invite/b/rj0ECz2c/59eee4dde6cda539a345e91554a92fdc/keystone-stein-roadmap <314:50
cmurphyhrybacki: sorry i meant the bluejeans meeting14:53
hrybackicmurphy: oh, we couldn't get it to work -- lbragstad is running me through the last few days of PTG on a hangout14:54
hrybackihttps://hangouts.google.com/call/lE9L6UGJeNeqO3WqT4nLAAEE cmurphy14:54
cmurphyah i probably don't need to be there then14:56
hrybackiyou're welcome all the same cmurphy14:57
hrybackicmurphy: we're about to go over the stein board now if you wanna join15:00
cmurphyhrybacki: okay i will in about 15 minutes, starting another meeting15:00
*** felipemonteiro has joined #openstack-keystone15:00
*** david-lyle has quit IRC15:04
*** dklyle has joined #openstack-keystone15:05
*** felipemonteiro has quit IRC15:06
*** mattgo has quit IRC15:07
gagehugoo/15:08
*** devx has joined #openstack-keystone15:14
hrybackicmurphy: we dropped btw15:24
cmurphyhrybacki: ya i noticed :)15:24
kmalloclbragstad: prob going to miss the meeting today, Dr appointment15:31
kmallocA lot fewer appointments starting next week.15:31
kmallocEither Thursday or Friday I'll be offline for a large chunk of the day.15:32
*** dave-mccowan has joined #openstack-keystone15:38
lbragstadkmalloc, sounds good - thanks for the heads up15:39
kmallochrybacki: as of right now can't make that meeting tomorrow.15:39
kmallocMight change today, but fwiw, Dr appointment is on the books until 10:30 Pacific (1.5 hours later than the meeting you set)15:40
hrybackikmalloc: ohhh, I misread that time15:46
hrybackikmalloc: hmm, so you and jaosorior are at odds when it comes to timezones15:47
kmallochrybacki: I will know in about 40 min if the appointment is cancelled for tomorrow.15:47
hrybackikmalloc: thank you!15:48
kmallocYeah, Pacific time sucks for coordinating with folks across the smaller pond.15:48
jaosoriorhrybacki: schedule it at a time where kmalloc can make it. I'm not required in that meeting until we actually start talking about deploying that.15:50
hrybackijaosorior: ack. Waiting to hear back on this appt. If it's still going on I'll move the meeting to later and update you15:51
*** belmoreira has quit IRC15:52
*** wlmbasson has quit IRC15:52
*** _d34dh0r53_ is now known as d34dh0r5316:05
*** pcaruana has joined #openstack-keystone16:07
*** felipemonteiro has joined #openstack-keystone16:08
*** shyamb has joined #openstack-keystone16:11
*** Emine has quit IRC16:12
*** dave-mccowan has quit IRC16:13
*** shyamb has quit IRC16:25
gagehugolbragstad should we look into suppressing the system scope warnings if it helps infra for the time being?16:28
lbragstadgagehugo oh - is that causing issues specifically?16:29
gagehugolooks like they're asking if we can clean up any deprecation warnings, or rather anything that is overly chatty16:30
lbragstadsure - we can look for ways to suppress it16:30
lbragstadmight just need a line to one of the setup classes in keystone16:31
lbragstador are they specifically looking for suppressing it in oslo.policy?16:32
*** ayoung has joined #openstack-keystone16:33
ayounglbragstad, kmalloc sorry I missed the meeting.  I am going to try and make 2 changes to Keystone to support Edge:16:37
ayoung1.  Optional Domain ID on create domain16:37
ayoung2.  optional "use the same logic as LDAP for Federated Ids"416:38
lbragstadwhat's the usecase for #1?16:38
ayounglbragstad, they go togeteher16:39
ayoungif I create the same domain in 2 keystones, and use the same ID, I can get matching userids16:39
*** dklyle has quit IRC16:40
ayoungits the way the LDAP code works for shadow users, and this means we can keep both LDAP and Federated IDs consistent without having to do Database level synchronization16:40
ayounglet me clarify16:40
ayoungoptional to allow the user to specify the domain ID when creating a domain16:41
ayoungit was requested and denied under dolphm years ago, but at the project level16:41
ayoungwe can punt on projects for the first go round, but for identity synch, it is kindof important16:41
lbragstadyeah...16:41
lbragstadthis came up recently...16:42
lbragstadlike in Sydney16:42
ayoungIts come up a few times16:43
ayoungI'd like to be able to run multiple Keystones within a single deployment, and not have to upgrade them in lock-step16:43
*** dklyle has joined #openstack-keystone16:44
lbragstadare you planning on using tokens between each region?16:45
ayounglbragstad, probably not16:45
ayoungmore likely K2K16:45
ayoungor something like a hub spoke setup16:45
ayoungHub will only know about other keystones16:46
ayoungAnd Federated Identity will match, so the user will have to get a new token when going from hub to spoke, so hub tokens are not valid anywhere but hub keystone16:47
lbragstadhmmm16:47
ayounglbragstad, tokens between would bring up lots of issues.  Fernet means "If I can validate, I can sign"16:50
ayoungso spokes would need to call back to hub in order to validate.  Might be OK, but means Hub has to be up16:50
cmurphywhat is the motivation for allowing setting id on create then? in the past reusing tokens was the use case and we pushed back hard on that16:52
cmurphywhy isn't basic k2k sufficient? we've been pushing either k2k or galera syncing as the right approach for edge16:53
ayoungcmurphy, so galera will work for , say 3 sites16:54
ayoungI am looking at deployments with 2016:54
ayoungeventually Galera is going to get scaled out16:54
ayoungbut lets look at K2K16:55
ayoungsay I have 2 sites (BOS and SFO) and I create a project in BOS.  I want to add an SFO user to it16:55
ayoungthat has to happen completely in the BOS Keystone16:56
ayoungbut what if I only have access to the SFO keystone?16:56
ayoungSo, I think K2K will work for some manual cases, but the user Ids then end up being distinct16:56
ayoungwhich for Audit is tough:16:57
ayoungI need to got user U from IdP I1  on Keyston K1 is User UU from IdP I1 on Keystone K216:57
ayoungcmurphy, the big thing is the predictable IDs16:58
cmurphyis auditing the only reason?16:59
ayoungcmurphy, now, we could do predictable Ids with Domain Name instead of ID.  Just we would have to change the LDAP code now, too, if we want to keep it consistent16:59
ayoungcmurphy, without predictable Ids, you can't do anything in a keystone for a user until they log in the first time16:59
ayoungno groups or role assignments are possible16:59
cmurphywe have the mapping api for that17:00
ayoungwith a predictable ID, you can pre-populate a user (potentially) and their resources are there ahead of time17:00
ayoungtrue17:00
lbragstad#startmeeting keystone-office-hours17:01
openstacklbragstad: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:01
ayoungHeh17:01
* lbragstad sigh17:02
lbragstad#endmeeting17:02
*** openstack changes topic to "Rocky release schedule: https://releases.openstack.org/rocky/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/wmyzbFq5/keystone-rocky-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:02
*** ChanServ changes topic to "Stein release schedule: https://releases.openstack.org/stein/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:02
openstackMeeting ended Tue Sep 25 17:02:26 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone_office_hours/2018/keystone_office_hours.2018-09-18-17.20.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone_office_hours/2018/keystone_office_hours.2018-09-18-17.20.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone_office_hours/2018/keystone_office_hours.2018-09-18-17.20.log.html17:02
cmurphyif the disk space on eavesdrop.o.o fills up i blame lbragstad17:02
lbragstadis that a challenge?17:02
cmurphylol17:03
* lbragstad accepts 17:03
lbragstad#startmeeting keystone-office-hours17:03
openstackMeeting started Tue Sep 25 17:03:16 2018 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: keystone-office-hours)"17:03
*** ChanServ changes topic to "Stein release schedule: https://releases.openstack.org/stein/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:03
openstackThe meeting name has been set to 'keystone_office_hours'17:03
lbragstadin reality though... i'm not sure meetbot is the best idea for office hours...17:03
ayoungcmurphy, we can map to a local account, I remember.  What is the "force create a user" option?17:03
cmurphyayoung: we can map to a local or ephemeral user17:04
cmurphyayoung: explain what is "force create a user" ?17:04
ayoungcmurphy, I think that is what happened to Anakin in episode 117:04
cmurphylol17:05
* ayoung ducks17:05
ayoungOK, so  say I am trying to keep 19 different openstack deployments in sync17:05
ayoungI am using a handful of LDAP sources17:06
ayoungthe user IDs from each one will be different17:06
ayoungIf I can say "the LDAP domain_id is AABBCC123 then they will all have the same userid as well17:07
ayoungthat is the absolute simplest case I can think of.17:07
ayoungI'd like to be able to match that logic in Federation, so I can get away from Simple Bind17:08
ayoungbut not treat users as Ephemeral17:08
ayoungand not have to modify the mapping files for any user-to-group assignments17:08
ayoungI'd like to be able to say "The BOS Keystone can control the RedSox domain and the SFO Keystone can control the Giants domain"17:09
ayoungand so forth.  Galera does not really let you do that. as all writes have to be synced everywhere17:10
ayoungbefore a commit is OKed17:10
cmurphyi'm not pushing galera i just know zzzeek we working on it17:10
cmurphywas*17:10
ayoungGalera is necessary, and will support a good number of use cases17:11
ayoungbut not all17:11
cmurphyis this just a question of usability? mapping rules are complicated and annoying but as far as i can tell they accomplish what you're trying to do17:11
ayoungIf you break the mapping, you break Keystone17:12
ayoungmodifying the mapping rules for an Idp is going to be a no-no17:12
ayoungit would be like recompiling your kernel just to launch a new executable17:12
ayoungYou don't have object level granularity, which denies RBAC access to manage it17:14
cmurphyI don't think it's fair to compare it to recompiling your kernel, it's more comparable to say modifying the mapping rules is like modifying your policy files, it's a pita and you could get it wrong but it's doable and sometimes necessary17:18
kmallochrybacki: appt is tomorrow, I expect to be free by 10am Pacific ( 1pm est)17:19
kmallochrybacki: that again might change later today (appt might be cancelled), but it is unlikely.17:20
kmalloclbragstad: meetbot is useless for office hours, we already log the channel17:20
hrybackikmalloc: okay, I'll move the meeting to that time (assuming I don't see others w/ conflicts)17:21
lbragstadyeah.. i agree17:21
lbragstadfor the most part i think the pattern is established17:21
lbragstadi'm not sure how often people reference the meetbot logs though17:21
* cmurphy runs away for a few minutes17:28
*** felipemonteiro has quit IRC17:28
lbragstadFYI - http://lists.openstack.org/pipermail/openstack-dev/2018-September/135016.html17:41
lbragstaddoes anyone else have suggestions for https://etherpad.openstack.org/p/BER-keystone-forum-sessions ?17:43
kmallochrybacki: need to push back the flask thing until later today17:51
kmallocLike... 1.5 hrs17:51
kmallocIf that is ok, just finished appointment and need food.17:51
kmallochrybacki: sorry.18:00
hrybackikmalloc: no worries18:01
*** aojea has joined #openstack-keystone18:13
ayoungI wish we could hide deprecation warnings in the unit tests18:39
openstackgerritMerged openstack/keystoneauth master: Reformat Adapter docstring  https://review.openstack.org/60504218:41
ayounglbragstad, any reason to maintain a strict 255 limit for Fernet tokens?18:51
*** dmellado has quit IRC18:53
*** raildo_ has joined #openstack-keystone18:53
jdennisknikolla, cmurphy: I found the problem with your SAML ECP message (can't find signature) and send knikolla an email with the explanation.18:53
*** raildo has quit IRC18:55
cmurphyjdennis: \o/18:55
ayoungjdennis, Did you ever tell me if/how it is possible to do SAML with HAProxy?18:55
openstackgerritayoung proposed openstack/keystone master: Replace UUID with sha256 generator for Federated users  https://review.openstack.org/60516918:56
openstackgerritColleen Murphy proposed openstack/keystone master: Convert legacy functional jobs to Zuul-v3-native  https://review.openstack.org/60245218:59
ayoungkmalloc, hrybacki ^^ is using the LDAP approach to generated IDs for Federated Identity.  The LDAP code is wicked convoluted, due to the whole "Mapping Backend" legacy stuff...This one hard codes the ID generator (which is another provider API) but really it should be injected19:01
jdennisayoung: it's in the federation doc I wrote: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/federate_with_identity_service/19:01
cmurphyjdennis: knikolla can you give me a tldr or forward me the details (colleen@gazlene.net) ? i've been meaning to come back to that for a while19:01
ayoungjdennis, thanks. I was actually looking at that earlier today, and was wondering if that was the issue you had raised.  Cool19:01
jdenniscmurphy: I just forwarded the email I sent to knikolla to you19:02
cmurphyjdennis: thanks19:02
jdennisayoung: not sure what issue you're referring to ...19:02
ayoungjdennis, this, specifically https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/federate_with_identity_service/introduction#haproxy_overview19:03
ayoungjdennis, I know that you were working on a fix of mod_auth_mellon to address it, and was not sure if that was something in the future.19:03
ayoungI think you said that the mellon fix was an improvement over just assuming that you were hitting the same HA proxy instance.  I need to present on this in a couple weeks, and had hoped to get that clarified before I lie to people on stage19:04
jdennisayoung: oh, you mean supporting shared session caches?19:04
kmallocayoung: the backend is complex/indirect, the behavior is all i'd like to see.19:04
kmallocayoung: take a known value and a supplied (from assertion) value and generate from that19:04
kmalloci don't care if we use the current code or something new/retro fit to make the current system suck less.19:05
ayoungkmalloc, that is basically what I did in that commit:19:05
kmalloc++19:05
ayoungjust I don't have a clean way to swap sha256 for shawhatevercomesnext19:05
jdennisayoung: if so, that code is 95% done, I'm in the process of testing it, then it will be sent upstream for review, so don't count on it soon (whatever soon means)19:05
kmallocayoung: look at how the pbkdf (bcrypt, scrypt) works, encode it like that19:05
ayoungjdennis, thank you.  That confirms what I was suspecting19:06
ayoungkmalloc, look at the review.  it is tiny19:06
ayoung https://review.openstack.org/60516919:06
kmallocright. follow up -> allow for shaxxxx -> newfangledhashingthing19:06
kmallochmm19:07
kmallocayoung: i worry, will that break anything for "current" federated users?19:07
ayoungkmalloc, nope19:07
kmalloccool.19:07
ayoungkmalloc, the concern I have is that it will break fernet19:07
kmallochmm.19:07
ayoungas, I think, it makes IDs slightly longer19:07
kmallocfernet doesn't care about strict id length19:08
kmallocit cares about total token length19:08
ayoungbut...that means fernet would fall down on LDAP ids, too19:08
kmallociirc.19:08
kmalloci'll need to dig to be sure.19:08
ayoungI saw a few warnings that lenght was 289, longer than max of 25519:08
kmallocyeah, then it might be a concern19:08
ayoungis that for revocations?19:09
ayoungif so, it is going to be a problem for LDAP as well, as those IDs are already sha25619:09
errrjdennis: on osp do you know if yall have plans to make it so you can set the needed bits in the haproxy config from one of the yaml puppet over ride files for the deploy-osp.sh file?19:12
errrjdennis: also the apache overrides..19:12
errrjdennis: lots of manual steps to get federation working on that platform because of that :(19:13
jdenniserrr: yes that is a well know issue. We do have plans to integrate it into tripleo sometime soon but the exact schedule has not been set yet19:15
ayoungkmalloc, what is interesting is that I saw that message before I changed the lengths in that test, but once I did, the lenght warning went away, too.19:15
errrjdennis: ok, well its good to know its at least on the radar19:15
jdenniserrr: not to worry, customers are faced with the issue and customers get attention :-)19:16
errr;)19:16
ayoung'Fernet token created with length of 290 characters, which exceeds 255 characters'19:16
ayoungerrr, from people like me19:16
errrayoung: me too :)19:17
hrybackikmalloc: I'm gonna have to depart in about ~45 mins. Think you'll have a chance to gander at my projects review on gerrit today? I've finally got it to where I can start to fix the failing tests but could use a sanity check before diving too deep19:46
kmallocok almost done19:46
hrybackifor simplicity: https://review.openstack.org/#/c/603451/19:46
kmallocsec. winding down a call19:46
hrybackikmalloc: ack -- me fetches a quick coffee19:46
kmallocok done19:48
kmalloci'll go get coffee too19:48
kmallocthen we can chat19:48
kmallochrybacki: sorry for the delay, has been a  long day19:48
hrybackikmalloc: no worries -- I live a life of sliding timelines :)19:51
kmallocback19:58
kmallocbluejeans?19:58
kmallocor irc?19:58
hrybackikmalloc: bluejeans is preferred (I'm visual)20:00
hrybackihttps://bluejeans.com/u/hrybacki/20:00
*** dmellado has joined #openstack-keystone20:07
*** mcape has joined #openstack-keystone20:23
mcapeHello all!20:28
mcapeI've run into trouble after queens->rocky keystone upgrade.20:28
mcapeMy s3 authorization is broken, clients receive message '<Code>SignatureDoesNotMatch</Code>'20:28
mcapeIn keystone logs, i see many 404 like "POST /v2.0/s3tokens HTTP/1.1. "20:28
mcapeI do not understand why swift proxy goes to the wrong address, any clues? Any help will be greatly appreciated.20:28
lbragstadmcape i believe the entire /v2.0/ path was removed in rocky, some of it was removed in queens but the s3 stuff was pulled afterwords20:30
mcapei just realized that probably this is wrong channel to ask support questions20:30
mcapethanks for your answer, and have a great day!20:31
lbragstadmcape yep!20:31
cmurphymcape: no this is the right channel to ask questions about keystone20:35
cmurphywe don't bite20:35
*** pcaruana has quit IRC20:43
kmallocmcape: please feel free to ask any questions about keystone, keystonemiddleware, keystoneauth, [and a myriad of other things we maintain] here... if it's thr wrong channel we're good about helping you find the right one20:47
kmalloccmurphy: i wont tell Nori (teh shiba) this channel is teeth free. She'd be a sad pupper (but she'll share her cow sans head stuffie with you)20:48
lbragstadok - i have two proposals for the forum submitted20:59
lbragstadone for generic operators and user feedback21:00
lbragstadand another for a session dedicated to keystone as an identity provider proxy21:00
mcapekmalloc: thank you for your willingness to help! i'm still stuck trying to fix my upgrade21:01
mcapewith help of @timburke i've managed to change the proxy' request to keystone to correct one21:02
lbragstadmcape so you're using v3 now instead of v2.0?21:02
mcapeyes i've added "auth_version = 3" to the [filter:s3token] section of proxy-server.conf21:03
cmurphykmalloc: :'D21:03
mcapebut now i receive error 50021:04
mcape<?xml version="1.0" encoding="UTF-8"?>#015#012<Error>#015#012  <Code>InvalidURI</Code>#015#012  <Message>Could not parse the specified URI</Message>#015#012</Error>#015#012: #012Traceback (most recent call last):#012  File "/usr/lib/python2.7/site-packages/swift3/middleware.py", line 80, in __call__#012    resp = self.handle_request(req)#012  File "/usr/lib/python2.7/site-packages/swift3/middleware.py", line 107, in handle_21:04
mcapeit is not complete, sorry21:05
lbragstadyou might be able to throw it in paste.openstack.org21:05
mcapehttp://paste.openstack.org/show/730906/21:06
timburkelooks like a swift3 problem more than a keystone one -- we might want to move this to #openstack-swift (and get some proxy-server logs)21:08
timburkebut while we're here... do we see the requests making it all the way to keystone? what's the response code if/when it gets there?21:09
mcapeno, keystone is not receiving requests21:11
timburkemcape: mind hopping over to swift's channel? i'll write up a bug for the first and most-obvious problem, then we'll get to figuring out the next step :-)21:14
mcapeokay, thanks!21:15
openstackgerritayoung proposed openstack/keystone master: Allow an explicit_domain_id parameter when creating a domain  https://review.openstack.org/60523521:15
ayounghrybacki, kmalloc, there is the other one.  I can file bugs or specs or whatever we want to do with them, or just release note it21:16
*** raildo_ has quit IRC21:17
kmallochm.21:18
kmallocrelease note should be fine, but a bug for tracking is nice.21:18
aningcmurphy: I setup another devstack, this time it's stable/rocky. But when I type in user name and password (myself/myself), and click on Login, I got an error:21:20
aningcmurphy: Error Message: No peer endpoint available to which to send SAML response21:20
aningcmurphy: have you ever seen this?21:20
cmurphyaning: check the testshib logs, it seems like there's a mismatching url between the metadata you gave to testshib and the endpoint the request is trying to return to21:25
aningcmurphy: k21:27
aningcmurphy: so that could mean I misconfig my entityID in metadata ...21:28
aningcmurphy: on my SP side, which would be the "peer endpoint" that the Idp sends the SAML2 response?21:30
cmurphyaning: probably not the entityID, that's just a unique string and not a real URL, but it could be the keystone endpoint in horizon's local_settings.py21:31
aningcmurphy: that endpoint is serviced by the browser, or by shibboleth mod?21:32
aningcmurphy: or Horizon?21:32
cmurphyaning: it's horizon that generates the special auth url where the saml response gets sent, and that endpoint is the one you set up in the keystone vhost21:36
*** mcape has quit IRC21:38
*** aojea has quit IRC21:58
*** mvkr has quit IRC22:22
*** mvkr has joined #openstack-keystone22:35
jdennisaning: entityID's are URN's not URI's, they are just a name, the endpoints are defined in the metadata with the triplet <service, binding, url>22:47
*** dklyle has quit IRC22:48
*** felipemonteiro has joined #openstack-keystone23:03
*** rcernin has joined #openstack-keystone23:07
openstackgerritMorgan Fainberg proposed openstack/keystone master: Add build_target arguement to enforcer  https://review.openstack.org/60188123:30
*** aojea has joined #openstack-keystone23:31
openstackgerritMorgan Fainberg proposed openstack/keystone master: Add build_target arguement to enforcer  https://review.openstack.org/60188123:32
*** stewie925 has joined #openstack-keystone23:33
*** aojea has quit IRC23:35
*** felipemonteiro has quit IRC23:41
stewie925hi keystonians23:46
*** aojea has joined #openstack-keystone23:54
*** aojea has quit IRC23:59
*** stewie925 has quit IRC23:59

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