SSO sign-in uses unknown vector:// URL type
See original GitHub issueDescription
Signing in to an internal chat server that uses SSO does not work as some of the browser-based flow is broken.
Steps to reproduce
- Start riot desktop application
- Click
Sign in
- Click
Change
to use our internal server, clickNext
- Click
Sign in with single sign-on
- Browser (firefox) window opens with our internal SSO page, where I log in
- Get a new browser page with
The application at vector is requesting full access to your <censored> Matrix account. If you don't recognise this address, you should close this browser window.
, plus a button withI trust this address
- Pressing the address button redirects the page to a URL reading
vector://vector/webapp/?homeserver=...
- Browser gives error
The address wasn’t understood
Describe how what happens differs from what you expected.
The browser should probably open the riot application with the verification info in the URL, but that doesn’t work, as the vector://
type isn’t understood… This issue seems similar, but it mentions a “riot://” URL, plus I’m not using the flathub version of the application.
Is there a way to manually give back the login URL to the riot-desktop
application? I check the command-line params but don’t see a relevant option.
Version information
- Platform: desktop
- OS: Arch Linux
- Version: 1.5.13 (note: the latest available version in the Arch repos is currently 1.5.12, I updated the PKGBUILD locally and built it to check if the SSO updates in 1.5.13 helped with the issue, but they don’t)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:42 (21 by maintainers)
Top Results From Across the Web
switch to https:// redirect url for SSO login to improve "do you ...
By the way, I strongly suggest using something like https://desktop.element.io as redirect URI, and host there a page that opens the element:// ...
Read more >Single Sign-On (SSO) - Vector LMS Support
Single Sign-On (SSO) allows a logged-in user (authenticated user) on one system to directly ... You can use the following link to login...
Read more >Attacking SSO: Common SAML Vulnerabilities and Ways to ...
In this blog I'll share some pointers that can be used when testing Single Sign-On (SSO) solutions that utilize SAML.
Read more >Unable to login as the service principal - Tomcat SSO to Active ...
As I have configured as SSO am wondering why tomcat prompting me to provide username and password. Usually before setup SSO we use...
Read more >Phishing for AWS credentials via AWS SSO device code ...
AWS SSO is vulnerable by design to device code authentication phishing, providing a powerful phishing vector for attackers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Note for others facing this issue on Arch: it’s due to the
.desktop
file included in theriot-desktop
Arch package. The issue is being tracked in this Arch bug report. The fixed.desktop
file in the bug patch (with the things @t3chguy suggested) solves the issue, just waiting on the package to be updated, now.Linked issue https://bugs.archlinux.org/task/66324?project=5&string=riot-desktop was closed on the 6th of May.