[kepler-dev] adding user login interface to Vergil

Laura L. Downey ldowney at lternet.edu
Tue Sep 13 08:19:24 PDT 2005


A few additional comments....

No worries Matt on not commenting on the log in and authentication screens.
I put them together quickly.  The mockups were to give the general design
idea that goes along with the proposed overall re-design.  

The reason I suggested to Zhije to have a look was not to imply that it was
a final design but just to give an idea of the overall design so that he
didn't mock something up that didn't fit.  Just trying to get us moving in
the general direction of the proposed re-design as we make changes so we
have less to change later on when we get the full re-design implemented.

The wording on the dialogs can easily be changed and I even made reference
to that.  Deana made the same comment about the word "demo" being used and I
only used it because it is used in the problem description on the wiki page
(demo account).  No problem with choosing something different.  Same goes
for the placeholder "email XXX for an account."  I didn't have anything
specific so just stuck that in there.

As to the user being prompted to log in, Ilkay and I discussed that and it
was my understanding that was the way things were to be designed so I went
with that.  I don't think users would be confused at having to log in to the
application at the beginning, I believe that is fairly standard on
networking applications that use distributed resources.  And people using
the local resources versus grid resources is analogous to working offline
and online which is also somewhat standard in networked applications.

I think it would be more confusing for the user not to be prompted to log in
and think they have access, only to realize later they don't and have to go
looking for a place to "log-in" to get access to other resources.  Logging
in at the beginning of a session or use of an application seems the most
logical and standard approach to me.  And if users consciously log out, then
want to log back in, they are aware because they made the choice.  But to
just open the app and expect them to know they are not logged in doesn't
seem the best design in my experience.

In terms of the issue of resources, that is a general term and could mean
"domain" if we need it to.  Perhaps I have misunderstood the requirements
here but I thought it was necessary that users know what they have access to
and what they don't.  I know if I was a user this information would be
important.  Especially if they are doing searching and see a resource
returned but can't get it because they don't have permission etc.  Or if
they want to run a workflow remotely but don't have access to the domain or
resource that workflow is on.

Again, the mockups were designed as an interim solution until we get a more
sophisticated role-based access model working which may make the problem of
knowing which resources a user has access too a moot point.

Laura L. Downey
Senior Usability Engineer
LTER Network Office
Department of Biology, MSC03 2020
1 University of New Mexico
Albuquerque, NM  87131-0001
505.277.3157 phone
505.277-2541 fax
ldowney at lternet.edu
 
-----Original Message-----
From: Jing Tao [mailto:tao at nceas.ucsb.edu] 
Sent: Monday, September 12, 2005 4:55 PM
To: Zhijie Guan
Cc: Laura L. Downey; kepler-dev at ecoinformatics.org
Subject: Re: [kepler-dev] adding user login interface to Vergil

Hi, Zhijie:

See my comment below the text.

Jing Tao
National Center for Ecological
Analysis and Synthesis (NCEAS)
735 State St. Suite 204
Santa Barbara, CA 93101

On Mon, 12 Sep 2005, Zhijie Guan wrote:

> Date: Mon, 12 Sep 2005 13:32:34 -0700 (PDT)
> From: Zhijie Guan <guan at sdsc.edu>
> To: Laura L. Downey <ldowney at lternet.edu>
> Cc: kepler-dev at ecoinformatics.org
> Subject: Re: [kepler-dev] adding user login interface to Vergil
> 
>
> That post is realy great. Sorry I forgot to get track on this. I did
> check the prototypes when you posted, and thought they were just a general
> idea instead of real implementation. It's my fault.
>
> Just a few comments. I cannot post it on wiki pages since I do not have an
> account yet.
>
> 1. The Kepler user may not "have to" log in before using Kepler. Though
> most of our users will be registered with the GAMA server, we still have
> some users who do not belong to any current-known group. An anonymous user
> account may be the alternative solution. But I doubt the users would like
> to log in when they just want to use their local resources. That's why I
> suggest the authentication dialog is integrated as a menu entry. So users
> can log in when necessary.
>

I agree with you. If user didn't log in, it runs kepler as public and 
he/she has a limit to access some resources.


> 2. For the "domain" part, I am not sure if we still need to know the
> user's domain(s). I remember Jing said the GAMA server (actually the
> MyProxy) could contact various LDAP servers to get the user
> authentication. In that case, no domain info is needed. We can either use
> the user-inputed domain info to locate the LDAP server, or let the GAMA
> server do the flooding search.
>

Does the domain mean Organization? If it does, I think we need the domain 
part, otherwise user should input the string  looks like 
"uid=john,o=NCEAS...". It is pain for user.

MyPoxy can contact to one main LDAP server, and main LDAP may referral to 
another LDAP server according to organization info for the user. So our 
system need domain info and it is convenient for user just select an 
domain for option list.


> Jing: Since we have the user interface already, should we start the design
> of the AuthenticationManager as you mentioned?
>
Yep, we can start it now. We can discuss it with matt, lkay and efrat.


> Thanks!
>
> Zhijie
>
>
> On Mon, 12 Sep 2005, Laura L. Downey wrote:
>
>> I'm confused.  I made a post to seek-dev about the log-in screen and
pointed
>> people to the wiki some time ago.  Here's the url to the log-in and
>> authentication mockups:
>>
>> http://kepler-project.org/Wiki.jsp?page=KeplerAuthenticationFramework
>>
>> I asked for feedback and got a few minor comments.
>>
>> The proposal was for the user to have to log in before getting to the
other
>> Kepler screens so not really a need for a log-in menu item -- this was a
>> first cut solution until we add in more sophisticated role based access
etc.
>>
>> Laura L. Downey
>> Senior Usability Engineer
>> LTER Network Office
>> Department of Biology, MSC03 2020
>> 1 University of New Mexico
>> Albuquerque, NM  87131-0001
>> 505.277.3157 phone
>> 505.277-2541 fax
>> ldowney at lternet.edu
>>
>>
>> -----Original Message-----
>> From: Matt Jones [mailto:jones at nceas.ucsb.edu]
>> Sent: Monday, September 12, 2005 1:00 PM
>> To: Zhijie Guan
>> Cc: Laura L. Downey; kepler-dev at ecoinformatics.org
>> Subject: Re: [kepler-dev] adding user login interface to Vergil
>>
>> Zhijie,
>>
>> Those dialogs ahve already been prototyped but not fully reviewed before
>> implementaiton starts.  Maybe Laura could post them on the usability
>> page or somewhere else on the wiki so that we can all comment before you
>> start implementing?  Thanks,
>>
>> Matt
>>
>> Zhijie Guan wrote:
>>> Thanks for pointing me to the right issue. I've read the wiki webpage on
>>> http://kepler-project.org/Wiki.jsp?page=KeplerUsability, which includes
>>> the proposal of Kepler redesign and Kepler Symbology. It is quite
>>> interesting to see a new look of Kepler.
>>>
>>> For the changes I would make, they are only a menu entry and a user
login
>>> dialog. They should be easily adapted to any schema/rationale with minor
>>> changes on the source code. And finally I will submit my changes to
Ilkay
>>> for CVS check in.
>>>
>>> Thanks!
>>>
>>> Zhijie
>>>
>>> On Mon, 12 Sep 2005, Laura L. Downey wrote:
>>>
>>>
>>>> Before making lots of changes, I would suggest that you look at the
>> proposed
>>>> re-design for the user interface.  Also, I've already designed the user
>> log
>>>> in screens and generally how they will be integrated into that design.
>>>>
>>>> I'd post the pointer to the wiki page but I can't seem to get the
Kepler
>>>> project pages to display at the moment.
>>>>
>>>> Laura L. Downey
>>>> Senior Usability Engineer
>>>> LTER Network Office
>>>> Department of Biology, MSC03 2020
>>>> 1 University of New Mexico
>>>> Albuquerque, NM  87131-0001
>>>> 505.277.3157 phone
>>>> 505.277-2541 fax
>>>> ldowney at lternet.edu
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: kepler-dev-bounces at ecoinformatics.org
>>>> [mailto:kepler-dev-bounces at ecoinformatics.org] On Behalf Of Zhijie Guan
>>>> Sent: Wednesday, September 07, 2005 4:49 PM
>>>> To: kepler-dev at ecoinformatics.org
>>>> Subject: [kepler-dev] adding user login interface to Vergil
>>>>
>>>> Dear All,
>>>>
>>>> I get a question for editing the "graph editor" user interface. I am
going
>>>> to implement the single login user interface for Kepler authentication
>>>> framework. Thus, I need to add a menu entry into the "Graph Editor"
user
>>>> interface. When user click this menu entry, the system should pop up a
>>>> dialog to let user input username and password. But I don't know where
I
>>>> should start in order to edit the user interface (Vergil?). I am pretty
>>>> new to the Kepler code jungle. Could anyone point me any source
>>>> code/development documents that I should read?
>>>>
>>>> Thank you!
>>>>
>>>> Regards,
>>>>
>>>> Zhijie Guan
>>>>
>>>> _______________________________________________
>>>> Kepler-dev mailing list
>>>> Kepler-dev at ecoinformatics.org
>>>>
http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> Kepler-dev mailing list
>>> Kepler-dev at ecoinformatics.org
>>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>>
>>
>
>
>
>
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>



More information about the Kepler-dev mailing list