| Summary: | Ugly "FORMOpenIdUser" title on sign in popup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> | ||||
| Component: | Client | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | malgorzata.tomczyk, Szymon.Brandys | ||||
| Version: | unspecified | Keywords: | polish | ||||
| Target Milestone: | 0.4 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
John Arthorne
Created attachment 205350 [details]
Screen shot
This is how it works: All human-readable information is provided in the authentication plugin. They are rendered in the top right popup even if no 401 error was returned. When 401 is returned it contains minimum information: login form link and an ID of authentication that is used, for instance, to match what came from authentication plugin, to prompt you with all the human-readable information. But authentication plugin is not mandatory and if we don't have it we display what we've got. What happened in your situation is probably that when 401 was thrown the authentication plugin wasn't deployed yet. I remember that we used to do a request to preference service before installing all the plugins. This may be it. I'll double check whether it's possible that this prompt was displayed even if authentication plugin was installed. The other thing is that I can change "FORMOpenIdUser" for the domain, as long as we have a login form link. I added a domain information to those authentication services that supply a login form. I also added a human-readable label to authentication error, so that even if there is no authenticationPlugin deployed something readable will be displayed. It's not mandatory. You can verify if this is sufficient. |