overwrite of protocol handler |
||||||||
Issue descriptionChrome Version: 59.0.3071.115 OS: Windows customer domain configured with Single Sign On What steps will reproduce the problem? (1) configure using local group policy the policy RegisteredProtocolHandlers for mailto protocol to go to https://mail.google.com/a/${DOMAIN}/?extsrc=mailto&url=%s (2) open a link mailto, it will ask the SSO login and go to Gmail (3) log off Gmail (4) open another link mailto What is the expected result? ask the SSO login -> Gmail What happens instead? ask for Google login -> SSO login -> Gmail Workaround: in the Local Group policy RegisteredProtocolHandlers register two protocol handlers for mailto link: [ {"url": "https://mail.google.com/a/${DOMAIN}/?extsrc=mailto&url=%s","default": true, "protocol": "mailto"}, {"url": "https://mail.google.com/mail/?extsrc=mailto&url=%s", "default": false, "protocol": "mailto"} ] video of the issue: https://drive.google.com/open?id=0B01ZVp8vDQocRWtuWTFuTXlCMDQ Video of the workaround: https://drive.google.com/open?id=0B01ZVp8vDQoceXA0c2lTUmt5Yjg
,
Jul 24 2017
TE can try a repro and update the thread.
,
Jul 25 2017
Able to reproduce issue on Windows 10 with chrome #59.0.3071.115 on Skytap environment. Followed the issue as per steps and video mentioned in the comment #0 Attaching the screencast for reference. marcore@ could you please look into it and confirm that this exact issue you are facing? Thank You...
,
Jul 25 2017
,
Jul 26 2017
Able to reproduce issue on Windows 10 with chrome M58- #58.0.3029.110 on Skytap environment. Reproduced the issue as per steps/video mentioned in the comment #0
,
Aug 2 2017
kkaluri@ yes, it's the same issue.
,
Aug 22 2017
,
Aug 1
,
Dec 14
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 20
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by marcore@chromium.org
, Jul 19 2017