Lei, I think CMU_frontend is able to get user info through cookie. The issue is that entry.py needs to know who is the user. To realize that, the user info should have to be passed through a long chain:
CMU_frontend --->> Benyang's web page -->> entry.py -->> and then finally CMU_backend. Changing so much code might be risky at this stage. That's why i think the method i mentioned before should be easier. Thanks Br. Qihao On Sat, Jul 30, 2016 at 2:03 AM, Pan, Lei (398K) <[email protected]> wrote: > Hi Qihao: > > The idea of identifying a user from a pre-defined, hard-coded > url to username map would work. However a more automatic way > is for a client to find out who he/she is after logging on to > the provenance server. Is there a cookie or query mechanism > that we can leverage? The login mechanism you use may provide > some programming interface. > > Thanks, > -Lei > > On 7/29/16, 3:28 PM, "Qihao Bao" <[email protected]> wrote: > > >Hi all, > > > >*I have thought about the user mapping issue based on Benyang's suggestion > >yesterday*. As we know, each user would be assigned to a VM instance. > > > >*Lei,* > > > >I think you can get the instance URL inside of the entry.py? For example, > >you can get http://ec2-52-53-198-227.us-west-1.compute.amazonaws.com/ > >dynamically > >for one instance and another URL for another instance, right? > > > >So if you add a dict of 'I*nstance URL to UserId*' and still send UserId > >to > >CMU_provenance as identification, everything would still work and nobody > >else would have to change their code. > > > >What i can do is to provide you the mapping of 'UserName to UserID in > >CMU_provenance', since you already have the mapping of ' instance URL to > >UserName', you will be able to join them together. > > > >Thanks a lot. > > > > > >Qihao > >
