qa.restricted : enable register link for guest users

[danicahelb]

The double login for the qa site is confusing for our providers, even when given a step-by-step guide.

Decision:

qa.restricted.clinepidb.org:

• We will replace the generic login to the restricted site with personal credentials on the 1st screen (this will log users into their VEuPathDB account as well as into the site). @rbelnap will need to be consulted about bypassing the generic login
• Note: if no login is required to open the restricted site, providers accessing the study as a “Guest” may be confused as to why their study is missing
• Providers will only be able to see the UNRELEASED studies (and unreleased study cards) to which they have been granted access (ie, their studies). Study cards for other pre-release studies will NOT be visible. Study cards for all released studies will be visible, with same access restrictions as the live site
• ClinEpi staff will be able too see ALL unreleased studies

qa.clinepidb.org:

• Providers do NOT use this site
• We will keep the normal double-login (generic login information on the 1st screen, personal VEuPathDB login for ClinEpi staff to access all pre-release studies)

[SheenaTomko]

Possible variation on above request: On qa.restricted.clinepidb.org, do not show all released studies to users who log in, only show the studies where they are a study team member (whether unreleased or released)

Pros:

1. Study providers wouldn’t have to search for their study
2. It would make qa.restricted look more different from the live site, which might help people remember which site they are looking at (often have people trying to view their study for qa on the live site…)
3. It would make the site truly seem more "restricted," which might ease the minds of groups who are more concerned about data getting out too early

Cons

1. Users couldn't easily compare their study to one done by another group unless they pulled up that other study on the live site

[dmfalke]

I thought we had decided to ask Bob to remove the initial "gateway" login from qa.restricted.clinepidb.org, and that website users would only be able to see studies that they have access to (even "public" studies would not appear for a user if they don't have explicit access). I think this will simplify things greatly from both a development perspective, and from a provider perspective. We might even want to change the url to provider.clinepidb.org?

[danicahelb]

@dmfalke, some thoughts:

• I agree, it would be nice to change url to provider.clinepidb.org

• I agree, it will help providers if they only see studies they have explicit access to. this can be a combo of released & unreleased studies (and not just unreleased)

• if we remove the initial "gateway" login, providers who navigate to provider.clinepi would essentially see an empty website, which would be confusing. if it is possible for providers to use their VEuPathDB login credentials on the "gateway" login page, they would automatically see their studies.

[dmfalke]

I think we could make this site show a login page if the user isn't already logged in.

[danicahelb]

needs sys admin attention, may be delayed by bob B's departure

[dmfalke]

Just to reiterate my idea, I think we should consider the following:

1. Remove the "gateway" login
2. If the user is not logged in with veupathdb credentials, redirect them to the veupathdb login site. They will be redirected back to the website once they enter their credentials.

[SheenaTomko]

This looks great. Systems removed the gateway login, and now the user is automatically directed immediately to log into their ClinEpi account. Private studies are accessible only to those with study access

[dmfalke]

I'm reopening this because we need to allow guest users to access https://qa.restricted.clinepidb.org/ce.restricted.qa/app/user/forgot-password and to register

[aurreco-uga]

this seems done