JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MOONSHOT-COMMUNITY Archives


MOONSHOT-COMMUNITY Archives

MOONSHOT-COMMUNITY Archives


MOONSHOT-COMMUNITY@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MOONSHOT-COMMUNITY Home

MOONSHOT-COMMUNITY Home

MOONSHOT-COMMUNITY  June 2011

MOONSHOT-COMMUNITY June 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: [UI] Error case in the identity provisioning

From:

Maria Turk <[log in to unmask]>

Reply-To:

Moonshot community list <[log in to unmask]>, Maria Turk <[log in to unmask]>

Date:

Tue, 28 Jun 2011 11:09:44 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (47 lines)

On 28/06/2011 00:44, Sam Hartman wrote:
>>>>>> "Maria" == Maria Turk<[log in to unmask]>  writes:
>      Maria>  Hi, OK yes, so with regard to removing the service ID card
>      Maria>  association when there is an error I can see a few usability
>      Maria>  issues cropping up here.  first off what sort of errors if
>      Maria>  it's all errors then we risk removing the association when
>      Maria>  error is temporary which is annoying to the user.  If we are
>      Maria>  sure that its an error that is permanent then we still have a
>      Maria>  problem because the user has specifically requested to add
>      Maria>  this association.  My immediate thoughts are if removing the
>      Maria>  association is important because we don't want the user to
>      Maria>  have to go through looking up the service and removing it
>
> In the April meeting we discussed and I believed agreed that having
> users go and look up a service and remove associations was always the
> wrong answer.  I thought we were looking at a mechanism where the user
> could enter a mode where they were always prompted but the current
> association was the default.
> The open question in April was how to signal this to the user.
> What was the resolution of that?
Yes that's true and it's still not a good answer because there might be 
an error.  So what I'm suggesting is this.   The user tries to connect 
to a service via the application and GSS-API for the first time.  The 
user is presented with a list of ID Cards.  The user selects one of 
those ID Cards.  The ID Card is then verified and authenticates against 
the service.  After everything does well and is successful the user is 
presented with a dialog suggesting everything has gone well and if they 
would like to always user this ID Card with this service.  This is the 
case when things go well.  When things don't go well the user never sees 
the association dialog and so no association occurs.

>      Maria>
>      Maria>  then we should only ask for the association (via the dialog)
>      Maria>  after we connect to the service with no errors.  This way
>      Maria>  there can not be an association unless all is well.
>
> How do we know what identity to use to connect to the service if we have
> not yet asked for the identity?
We will ask for the indentity
> Also, what about simply marking the association for reconfirmation
> rather than actually removing it. Effectively present the dialogue next
> time with the current association selected but with the option to
> change.
If the dialog only appears when there is a success we will not need to 
remove anything.  The association will only be set when everything goes 
well.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2022
December 2021
October 2021
September 2021
August 2021
June 2021
April 2021
February 2021
January 2021
December 2020
November 2020
October 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
January 2020
November 2019
October 2019
September 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
June 2018
April 2018
November 2017
October 2017
September 2017
August 2017
July 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager