{"action":"created","issue":{"url":"https://api.github.com/repos/ScienceCommons/api/issues/186","labels_url":"https://api.github.com/repos/ScienceCommons/api/issues/186/labels{/name}","comments_url":"https://api.github.com/repos/ScienceCommons/api/issues/186/comments","events_url":"https://api.github.com/repos/ScienceCommons/api/issues/186/events","html_url":"https://github.com/ScienceCommons/api/issues/186","id":89950756,"number":186,"title":"Improve login page to clarify workflow for non-invited users","user":{"login":"eplebel","id":4512335,"avatar_url":"https://avatars.githubusercontent.com/u/4512335?v=3","gravatar_id":"","url":"https://api.github.com/users/eplebel","html_url":"https://github.com/eplebel","followers_url":"https://api.github.com/users/eplebel/followers","following_url":"https://api.github.com/users/eplebel/following{/other_user}","gists_url":"https://api.github.com/users/eplebel/gists{/gist_id}","starred_url":"https://api.github.com/users/eplebel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eplebel/subscriptions","organizations_url":"https://api.github.com/users/eplebel/orgs","repos_url":"https://api.github.com/users/eplebel/repos","events_url":"https://api.github.com/users/eplebel/events{/privacy}","received_events_url":"https://api.github.com/users/eplebel/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ScienceCommons/api/labels/high%20priority","name":"high priority","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-06-21T19:32:47Z","updated_at":"2015-07-14T01:07:33Z","closed_at":null,"body":"Now that we have the beta site working for unauthenticated users, I just noticed that if a non-invited user clicks on \"log in to edit/add...\" on an article page, they're brought to the login page, but it's completely unclear that they actually *cannot* login if they haven't been invited. Hence, login page needs to be improved as follows:\r\n![login-page-issue](https://cloud.githubusercontent.com/assets/4512335/8551979/09fc300c-24a8-11e5-8bc0-8e0843fc6755.png)\r\n\r\nThe following change also needs to be implemented:\r\nIn the event a non-invited user nonetheless tries to login on this page, they should get a message popup that states: <i>\"You are attempting to log in using an email address that has not been invited into the system. Please use the email address with which you were invited into the system or register to be notified when our public Beta will be ready.\"</i>, and remain on the login page. Currently non-invited users trying to login end up on the Sign up section of the landing page (https://www.curatescience.org/#section-6)\r\n\r\nSteps to reproduce this last issue:\r\n1. Go to login page, https://www.curatescience.org/beta#/login\r\n2. Attempt to sign in using a gmail address that has *not* been invited into the system (i.e., *not* on the whitelist)\r\n\r\nRESULT: After giving Curate Science permission to access Google+ account info, notice that you end up on the Sign up section of the landing page (https://www.curatescience.org/#section-6)\r\n\r\nEXPECTED: User should get a message along the lines of: <i>\"You are attempting to log in using an email address that has not been invited into the system. Please use the email address with which you were invited into the system or register to be notified when our public Beta will be ready.\"</i> and remain on the login page.\r\n\r\nThis link might provide a clue to how to fix the problem:\r\nhttps://www.curatescience.org/auth/failure?message=csrf_detected&strategy=google_oauth2"},"comment":{"url":"https://api.github.com/repos/ScienceCommons/api/issues/comments/121103438","html_url":"https://github.com/ScienceCommons/api/issues/186#issuecomment-121103438","issue_url":"https://api.github.com/repos/ScienceCommons/api/issues/186","id":121103438,"user":{"login":"eplebel","id":4512335,"avatar_url":"https://avatars.githubusercontent.com/u/4512335?v=3","gravatar_id":"","url":"https://api.github.com/users/eplebel","html_url":"https://github.com/eplebel","followers_url":"https://api.github.com/users/eplebel/followers","following_url":"https://api.github.com/users/eplebel/following{/other_user}","gists_url":"https://api.github.com/users/eplebel/gists{/gist_id}","starred_url":"https://api.github.com/users/eplebel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eplebel/subscriptions","organizations_url":"https://api.github.com/users/eplebel/orgs","repos_url":"https://api.github.com/users/eplebel/repos","events_url":"https://api.github.com/users/eplebel/events{/privacy}","received_events_url":"https://api.github.com/users/eplebel/received_events","type":"User","site_admin":false},"created_at":"2015-07-14T01:07:33Z","updated_at":"2015-07-14T01:07:33Z","body":">>>>An easier way might be to use some JavaScript to make the flash message\r\ndismissable (with an 'X' button) or have it automatically disappear after a\r\nfew seconds, or both. What do you think?\r\n\r\nThat would be awesome! \r\nI'd say have an 'X' button that users can click to dismiss the message *and* also automatically dismiss it after 5 seconds."}}