Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337038

Summary: [user] Better usability on 403 pages
Product: [ECD] Orion Reporter: John J. Barton <johnjbarton>
Component: ServerAssignee: Malgorzata Janczarska <malgorzata.tomczyk>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse, simon_kaegi, Szymon.Brandys
Version: 0.2   
Target Milestone: 0.2   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
screenshoot none

Description John J. Barton CLA 2011-02-12 12:18:44 EST
The current 403 page is
-------------
HTTP ERROR 403

Problem accessing /file/A/extensions/dyne/branches/dyne0.1/doc/index.html. Reason:

    FORBIDDEN

Powered by Jetty://
-------------

The page should:
  tell you what user-id you are currently using (eg openid johnjbarton)
  explain that the user-id for the requested page does not match 
  link to the login and to the navigator page
Comment 1 Szymon Brandys CLA 2011-09-26 05:56:09 EDT
It is not only html calls. I would also improve xhr calls handling.
Comment 2 Malgorzata Janczarska CLA 2011-10-20 12:21:12 EDT
The change is released to branch bug33038.
I had to use authentication service to generate the 403 error. In displays error information and login form.
To get 403 in html (plain) call
1. login
2. go to 
<host>/users/B (or whatever is not your user URI)
<host>/workspace/C (or whatever is not your workspace)
etc.

This is all about plain HTML calls, not the ones made from out client in dojo.
Comment 3 Malgorzata Janczarska CLA 2011-10-20 12:22:56 EDT
Created attachment 205659 [details]
screenshoot
Comment 4 Malgorzata Janczarska CLA 2011-10-20 13:01:52 EDT
I'm not sure if this is a good solution. Moving to 0.4 hoping to get others opinion.
Comment 5 Anthony Hunter CLA 2014-06-16 12:12:13 EDT
(In reply to Malgorzata Janczarska from comment #4)
> I'm not sure if this is a good solution. Moving to 0.4 hoping to get others
> opinion.

The 403 error says:
You are not authorized to access /workspace/{user}-OrionContent

I agree this is sufficient.