Design

Version 1.1 of section E.2.5 is more extensive than the previous version and introduces new requirements.  As stated in version 1.1, all of the points listed are required from all clients.

In Section D,  I think it would be safe to remove my notes about the flow diagram that you included just before the diagram. You covered all of those points in the document text already, so they're unnecessary.

In Section D, there are some sizable pieces of text and images arguing why the proposed design makes sense. These distract from the presentation of the design and aren't helpful to people who are only trying to follow the design in their work.

As a member of the Globus team at UChicago, I would be delighted if XSEDE chose to feature Globus prominently on its login buttons!  And I agree with the rationale presented for why that would make sense.

In Section C, please remove the suggestions about how Globus should market itself.

These aren't necessary elements of the XSEDE Web SSO design and seem to be for a different audience.

In the scheme of things, this perhaps isn't a big deal.  I noticed that Section B (Introduction) doesn't describe what's in this document clearly.

Hi Lee,

I have gone over the Globus Auth spec and have the following questions/notes:

Just planting a flag - I am writing up a number of questions and comments on this design document. I'll post them ASAP.

Short version: I do NOT approve of this design as currently described.

- Derek

I think we should disallow Globus Auth custom skins for individual XSEDE apps because of the increased susceptibility to Phishing attacks and to keep the XSEDE Web Single Sign-On interfaces as uniform as possible.  Also, XSEDE app developers would need to remember to update custom skin logos, fon

A few things:

1. For some reason the PDF shows as every other page is blank, it makes the document hard to read.