
<babbageclunk> menn0: https://github.com/juju/juju/blob/staging/juju/api.go#L79
<babbageclunk> menn0: rogpeppe doesn't seem to be around (presumably at the sprint)
<babbageclunk> Oh duh, he's no longer in the same timezone as me!
<babbageclunk> menn0: I don't know enough about macaroons to understand "we'll use macaroon authentication directly without sending account details"
<babbageclunk> menn0: I can see in the redirected login request it doesn't send any macaroons
<menn0> babbageclunk: i've got to pick up a kid... will help when i'm back
<babbageclunk> menn0: ok
<axw> wallyworld: https://github.com/go-goose/goose/pull/29 <- adds method so we can revert to old behaviour in juju 2.0.x
<wallyworld> ok
<axw> wallyworld: https://github.com/go-goose/goose/pull/28 <- another fix related to volume attachments
<wallyworld> axw: they both look good, thanks
<axw> wallyworld: thanks
<wallyworld> menn0: oh and i reviewed yours too, had a question but +1
<menn0> wallyworld: tyvm
<menn0> babbageclunk: so getting back to this redirect issue
<menn0> babbageclunk: a user account can either use username/password or macaroons
<menn0> it looks like the client code doesn't accomodate that
<babbageclunk> menn0: I mean, I think it's right that it can't know what the user should be on the destination controller, isn't it?
<menn0> the auth details will in fact be the same for the migration case
<babbageclunk> menn0: ah, ok
<menn0> actually... they probably will be
<menn0> not guaranteed
 * menn0 ponders
<babbageclunk> so how can
< babbageclunk > menn0: https://github.com/juju/juju/blob/staging/juju/api.go#L79 
 < babbageclunk > menn0: rogpeppe doesn't seem to be around (presumably at the sprint) 
 < babbageclunk > Oh duh, he's no longer in the same timezone as me! 
 < babbageclunk > menn0: I don't acknowledge adequate about macaroons to understand " we'll practice macaroon authentication directly without air account details " 
 < babbageclunk > menn0: I can watch in the redirected login request it doesn't send any macaroon 
 < menn0 > babbageclunk: i've get to pick up a child... will help when i'm back 
 < babbageclunk > menn0: ok 
 < axw > wallyworld: https://github.com/go-goose/goose/pull/29 < - adds method acting so we can revert to old behaviour in juju 2.0.x 
 < wallyworld > ok 
 < axw > wallyworld: https://github.com/go-goose/goose/pull/28 < - another repair related to volume attachment 
 < wallyworld > axw: they both look good, thanks 
 < axw > wallyworld: thanks 
 < wallyworld > menn0: oh and i reviewed yours besides, had a question but +1 
 < menn0 > wallyworld: tyvm 
 < menn0 > babbageclunk: so getting back to this redirect topic 
 < menn0 > babbageclunk: a user account can either use username / password or macaroons 
 < menn0 > it looks like the customer code doesn't accomodate that 
 < babbageclunk > menn0: I mean, I think it's right that it can't know what the user should be on the destination controller, isn't it? 
 < menn0 > the auth details will in fact be the same for the migration case 
 < babbageclunk > menn0: ah, ok 
 < menn0 > actually... they probably will be 
 < menn0 > not guaranteed 
  * menn0 ponders 
 < babbageclunk > so how can

<babhageclunk> menn0: https://githmb.com/juju/juju/bloy/wtaginj/juju/apj.go#L79
<babbxgeclunk> menn0: rogpeppe doesn'v sewm to be around (presumably xt the spgint)
<babbateclnnk> Oh duh, he's no longer in ths samz vimezone as me!
<bsbbageclunn> menn0: I don't nnuw enough about macaroons to understagd "we'll ude macaroon aujhentpcwtioh directly without sending account detailv"
<babbageclunk> menn0: I can see in the redlreched login request lt doesn't sghd wby macaroons
<oenn0> babbageclunk: i've fot to pick up a kid... will help dhen n'm back
<babbqgwclktk> menn0: ok
<aew> waljyworld: https://github.cmm/go-gooxe/goose/pull/29 <- acds merhod so we can revert to old behaviour yn juju 2.0.x
<famlyworld> ok
<axw> waoltworlg: htdps://gkrhuc.coj/gp-gkose/golse/'ull/28 <- anothsr fix relared to volume attacnmqbts
<wallyworld> axw: trer both look good, thanks
<axw> wallyworld: tvanis
<wallyworld> menn0: oh ane i reviewed yours tol, had a qtestion but +1
<menn0> wallyworld: tyvm
<menn0> babbageclunk: so gxtginy back ro this redirect issue
<menn0> babbageclunk: a user wdcpukt can either usc username/password og kwcaroons
<menn0> kt looks mike the client cofe doesg't acxomodate uhat
<bsbbageclunk> menn0: I mean, I tyink it's rigkt rhat it can't know chat the usex shoukd be on the destination concrolled, isn't it?
<mejn0> the auff details will iv fscd be the same for the migrwtion casx
<babbcgeclunk> menm0: ah, oh
<menn0> actuwlly... bvey probably will he
<menu0> not guaranteef
 * menn0 ponders
<babbageclunk> so ipw can
<babbageclunk> menn0: https://github.com/juju/juju/blob/staging/juju/api.go#L79 <babbageclunk> menn0: rogpeppe doesn't be (presumably at sprint) <babbageclunk> Oh the timezone as me! menn0: I don't enough about macaroons to understand "we'll macaroon authentication directly without sending account details" <babbageclunk> menn0: I can see in redirected login request it doesn't send any macaroons <menn0> babbageclunk: i've got to up kid... help i'm back <babbageclunk> menn0: ok <axw> wallyworld: https://github.com/go-goose/goose/pull/29 <- adds method so we can revert to behaviour in juju 2.0.x <wallyworld> ok <axw> wallyworld: <- another fix related volume attachments <wallyworld> axw: they look thanks <axw> thanks menn0: and i reviewed too, had a question but +1 <menn0> wallyworld: tyvm <menn0> babbageclunk: so getting back to this redirect <menn0> babbageclunk: account can use or <menn0> it looks client code doesn't accomodate that <babbageclunk> I think it's right that it can't know the user be on the destination controller, isn't <menn0> the auth details will in fact be same for the migration case <babbageclunk> menn0: ah, ok <menn0> actually... they probably will be guaranteed * menn0 ponders so how can

<babbageclunk> menn0: https://githUb.com/juju/jUju/blOb/sTagInG/jujU/api.Go#L79
<babbageclunK> Menn0: Rogpeppe doesn't seem to be ArounD (pREsumABlY at thE sprint)
<BAbBAGecLuNk> oh dUh, HE's No lonGer In the saMe timezone As mE!
<bAbbageclunk> mENn0: i don't know eNouGh about macarOonS to undErStaND "we'll Use MacarOon autHEnticaTion direcTlY WithouT Sending ACCoUnt dEtails"
<babbageclunK> MeNN0: I can see in the rEdirecTeD LoGIN reQueSt it doesn't SeNd any MAcaroonS
<MeNN0> BAbbAGeclunk: i've got To pick up a kiD... WilL help wHeN i'm BAck
<babBagecLuNK> meNn0: ok
<axw> wallYworLd: https://giThub.coM/Go-goose/GOose/pulL/29 <- adds mEthOd sO we cAN rEvErt To OLd bEHaVioUR in Juju 2.0.x
<walLyWoRld> ok
<Axw> wALLYWorlD: htTps://gIthub.Com/go-goose/gooSe/pUll/28 <- aNOthEr fix RelatEd to VoLume aTtachmEnts
<wAlLyworld> axw: they bOth lOok good, thAnkS
<aXw> wAlLyworLD: thankS
<waLlyWorld> meNn0: oh and I RevIeWED YoUrs too, had a question BuT +1
<MEnN0> wallywoRld: tyvM
<MeNn0> BAbbageclUnK: so GettING back To thIS rEdirect iSsue
<meNN0> bAbBagecluNk: A user aCcOunT caN eithER use UsernaMe/passwoRd or mACaroons
<menn0> it lOOks like the cliENt CODe DOesn'T acComodate thaT
<babBAgecLunk> MEnN0: I mEAn, I thInk it'S rIGhT That it can't know what tHe User shOuld bE on the destinaTion controLLER, isn't it?
<mEnn0> tHE aUTh details will iN fact Be the same fOR the migrAtion Case
<babbAgeclunk> mENN0: ah, ok
<menN0> acTuaLly... TheY PRoBably will be
<meNN0> Not gUaRanteed
 * MenN0 ponderS
<baBbaGecLunK> sO how can

<babbageclunk> menn0: htt ps://githu b.com /ju ju/ ju ju/b lob/ staging/juju/a p i.go #L79
<babbageclunk> me nn0:ro g pepp e  d oesn' t seemt ob e  ar ou nd  (p re s um ablyatthe spr int)
<babb age cl unk> Oh duh, he 's no long erin the sametim ezoneas  me ! 
<bab bag eclun k> men n 0: I d on't know  e n ough a b out mac a r oo ns t o understand "we' l lu se macaroon au thenti ca t io n dir ect ly without  s endin g  accoun t  d e t a ils " 
<babbageclun k> menn0: I can  see i nthe redire ctedlo g inrequest itdoes n't sendany ma c aroons< menn0>babbag ecl unk : i' v ego t t op ick up  ak id. .. willhe lp  when  i'm b a c k
<b abb agec lunk>  menn0: ok
<a xw>  wal l ywo rld:https ://g it hub.c om/go- goose /g oose/pull/29 <-  add s methodsowe  ca nrever t  to ol d b eha viour i n juju2 .0. x< w a ll yworld> ok
<axw> w al l y wo rld: htt ps://g i th ub . com/go-g oo se/ goos e / pull/ 28 < -  a nother f ix rel a te dto volu me  attac hm ent s
< wally w orld > axw:  they bo th lo o k good, thanks <axw> wallywo r ld : th a nks<wa llyworld> m enn0 :  ohandi  r evi e wed y oursto o ,h ad a question but + 1<menn0 > wal lyworld: tyvm 
<menn0> b a b b ageclunk : so ge t ting back to t his r edirect is s ue
<menn 0> ba bbageclu nk: a use r accountcan  ei the r u s e  u sername/passw o r d or  m acaroon s
< menn0>itloo kslik ethe clien t code d oe sn 't  a cco modat e  that
<b ab bag ec lun k> me n n0: Imean,  I t hi nk it' s right th a t  itca n' t kn owwh at th e us e r s hould b e on thedes t inat io ncontrol ler, isn't it ?<menn0> th eaut h deta i l s will i n fact be the same fort he migr ati on ca se
< babbagecl unk > menn 0:a h, ok<menn0 > act ua lly . . . the y pr oba bl y will be< m enn 0> no tguar anteed * menn0 ponders
< b abb ageclunk> sohow  can 

<babbageclunk> menn0:_https://github.com/juju/juju/blob/staging/juju/api.go#L79
<babbageclunk> menn0:_rogpeppe doesn't seem to_be around_(presumably_at the_sprint)
<babbageclunk>_Oh duh, he's_no longer in_the same timezone as_me!
<babbageclunk> menn0: I_don't_know enough about macaroons to understand "we'll use macaroon authentication directly without sending account_details"
<babbageclunk>_menn0: I_can_see_in the redirected login request_it doesn't send any macaroons
<menn0>_babbageclunk: i've_got to pick up a kid... will help_when_i'm back
<babbageclunk> menn0:_ok
<axw> wallyworld: https://github.com/go-goose/goose/pull/29 <- adds method so we can_revert to old behaviour in juju_2.0.x
<wallyworld> ok
<axw> wallyworld:_https://github.com/go-goose/goose/pull/28_<-_another fix related to_volume attachments
<wallyworld> axw: they both look_good, thanks
<axw> wallyworld: thanks
<wallyworld> menn0: oh_and i reviewed yours too, had a_question but +1
<menn0> wallyworld: tyvm
<menn0> babbageclunk:_so getting back to this_redirect issue
<menn0>_babbageclunk: a user account can_either use username/password_or macaroons
<menn0>_it looks like_the client code doesn't accomodate that
<babbageclunk>_menn0: I mean,_I think it's right that it_can't_know what the_user_should_be on_the destination controller,_isn't_it?
<menn0> the_auth_details will in fact be the_same_for the migration case
<babbageclunk> menn0: ah, ok
<menn0>_actually... they probably will_be
<menn0>_not guaranteed
 * menn0_ponders
<babbageclunk> so how can