If you try to login to the Corvum portal, and are just looped back to the login screen, you're likely running into this cookies problem.
This login issue is due to a third-party cookie that is set by our login partner, Auth0, to handle the login process. This is required, and is no longer supported explicitly by all browsers.
Corvum does not track your Internet use at all, and we are not interested in gathering any information from your browser other than what is specifically required for the functionality of our service. Allowing this type of cookie to be placed on your browser for all sites can allow them to do things you may not otherwise like, so we recommend only allowing the Corvum portal to place this type of cookie, if possible.
In order to login, you can either:
- Set your browser to ONLY allow 3rd party cookies for the Corvum portal (supported by some browsers)
- Set your browser to allow 3rd party cookies for all websites (perhaps not ideal, so remember to come back later)
- Use a different browser (eg: Chrome / Brave) that lets you allow 3rd party cookies for particular sites, and allow this for https://beta.app.corvum.io/ only.
Safari: Allow 'Cross-site tracking' in 'Privacy' settings (note that this may allow tracking that you'd rather not prefer to allow).
Chrome: You can allow 3rd party cookies for a particular site:
(this can be found in 'Settings / Privacy and Security / Third-Party Cookies').
The Brave browser gives you easy controls by allowing you to turn its 'Shields down' for any particular site, while you're looking at it, which gives that site trusted access.
Firefox: The 'standard' level appears to allow the Corvum portal to work. However, you can also allow these cookies specifically for the Corvum portal.
Look for 'Manage Exceptions' in the top-right:
Edge:
You can create an exeption for the Corvum portal under 'Settings / Privacy, Search, and Services / Exceptions'.
Set 'Tracking prevention' to 'Balanced':
Tap 'Exceptions':
Tap 'Add a Site' and specify https://beta.app.corvum.io/:
Our team is currently reviewing what caused this issue and are working on a permanent resolution that doesn't involve this requirement.
Comments
0 comments
Article is closed for comments.