Grouper Developers Forum

[Gagné Sébastien <>]

UI is 2.1.0 (haven’t tried 2.1.1)

 

I’m not 100% sure about how CAS works, but I believe the app servers detects that the CAS ticket is expired and sends a redirect (302) to the login page. I believe the problem with the Lite UI is that the AJAX request inside a page won’t do a “regular” HTTP request and _javascript_ might not handle the redirect properly (if it was sent with these type of request).

 

If I do a request for the Lite UI home page directly I am prompted by the login page. The problem is when I try to do an action inside the page when the session is expired.

 

 

De : Chris Hyzer [mailto:]
Envoyé : 19 juillet 2012 14:45
À : Gagné Sébastien;
Objet : RE: Lite UI problems

 

What is the version of the Lite UI which has internationalization problems?  Have you tried in 2.1?

 

How does the browser know there is a problem with Authn?  Is there a 302 response from the app server when authentication is needed?  So if there is a 302 in ajax it should redirect to the same page which will trigger a logon?

 

Thanks,

Chris

 

From: On Behalf Of Gagné Sébastien
Sent: Thursday, July 19, 2012 2:39 PM
To:
Subject: [grouper-dev] Lite UI problems

 

Hello,

Using the lite UI I found some problems which would be nice if they were addressed in next UI

 

First, accent support is very iffy, we translated part of nav.properties, but sometimes (like on buttons) the html entities were shown (e.g. &eacute;) instead of the value (é). There’s some problems with encoding between Lite UI and Admin UI (one will show the character é while the other will show a question mark)

 

Also, if I enter some text for a grouper entity (an attribute in this case), accents are bugged :

Before Save:

After save :

 

 

Enough of our French eccentricity, there’s also a problem with CAS integration with the Lite UI :

 

We authenticate with CAS server and sessions expires after some time. This is no problem with the admin UI which will redirect you back to the login page to re-authenticate when you click on a link. However, this is not the case with the Lite UI, I will usually get a message box telling me that the XML request failed. If I re-authenticate using the Admin UI and go back in the Lite UI and do the same task, everything is back to normal. I believe this is because of the Ajax behind. It would be nice if there was a way to have a re-authentication (refresh the page maybe ? I think you need a new webrequest to have the app redirect you to the login page)

 

Thanks

 

 

Sébastien Gagné,     | Analyste en informatique

514-343-6111 x33844  | Université de Montréal,

                     | Pavillon Roger-Gaudry, local X-100-11