Chrome
- Desktop
- Go to Settings > Advanced Settings > Privacy and Security > Site Settings > Cookies and Site Data
- Make sure Cookies are enabled and “Block Third-Party Cookies” is turned off.
- We recommend you clear history and website data.
- Launch your browser, go to History or press CRTL + H > Clear website history
- Mobile App
- Go to Settings > Site Settings > “Cookies”
- Make sure Cookies are enabled and "Block Third-Party Cookies" is turned off
- We recommend you clear history and website data
- In Chrome, select the three dots on the lower right-hand corner of the device > tap History > tap Clear Browsing Data
Firefox
- Desktop
- Go to Options > Privacy and Security
- Make sure Cookies and Site Data are enabled and “Third Party Cookies” are not disabled.
- We recommend you clear your history.
- Press the menu (upper right-hand corner) then to Options > Privacy & Security > Under Cookies and Site Data, choose Clear Data
- Mobile App
- Go to Settings > Privacy > Cookies
- Set to “Enabled”
- We recommend you clear your history and cookies.
- On the bottom of the app, click the menu icon > Settings > Data Management > Website Data > Clear all data
Microsoft Edge
- Desktop
- Go to Settings > Privacy and Security > Cookies
- Set to “Don’t Block Cookies”
- We recommend you clear your history and cookies.
- On your computer, CTRL+H, select the three dots in the History menu > Clear Browsing History
Safari
- Desktop
- Go to Safari’s Preferences > Privacy > Block Cookies
- Set to “Never”
- If “Prevent Cross-Site Tracking” is enabled, please disable
- We recommend you clear your history and cookies.
- Safari > Menu > Clear History
- Mobile
- Go to Settings > Safari
- Set “Block All Cookies” to be disabled and “Prevent Cross-Site Tracking to be disabled as well.
- We recommend you clear your history and cookies.
- In the Settings > Safari > Select Clear History and Website Data
Why are Third-Party Cookies/Cross-Site Scripting required by Qwickly Attendance?
Qwickly Attendance integrates with your LMS by using API Tokens. API Tokens are generated by Qwickly Attendance on behalf of the logged-in user to request data from the LMS. In order to generate API tokens, Qwickly Attendance uses the 3-Legged Oauth authorization workflow. This workflow consists of the following steps:
- When Qwickly Attendance is launched, Qwickly Attendance redirects the user's request back to the LMS.
- The LMS verifies the logged user's identity, and redirects the request back to Qwickly Attendance with an authorization code.
- Qwickly Attendance uses this authorization code to generate the API token.
If a device has Third-Party Cookies disabled or Cross-Site Scripting is prevented (which also blocks cookies from being set), the user's session data is lost in redirecting for the authentication process, which is why an error is displayed to users.
Comments
0 comments
Please sign in to leave a comment.