-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird ios-only SSO cookie bug #2722
Comments
Hi @glebtv thanks for the report, that seems to be an issue with the library, have you considered submitting a pull request to the library directly? |
There is one already: Unfortunately, as per the library's readme it is unmaintained. If you are willing to use a fork, this fixes it:
|
A few of our users were seeing this as well. Updating to the latest version available from the app store resolved it for them. |
I'm still having this issue (where it just says status: ok) and I have the latest version of the app (released yesterday). |
@arcdigital make sure your server url matches the SiteURL in the system console |
It did, couldn't figure out how to fix it so we changed to a subdomain and it works now. |
Since the ios part of the cookie library is now pulled into mattermost-mobile for another issue, maybe fix this one there too? this is a one-line fix, see my first post |
@glebtv perhaps you could submit a PR for that? |
Submit feature requests to http://www.mattermost.org/feature-requests/. File non-security related bugs here in the following format:
Summary
Gitlab SSO does not work on iOS
Environment Information
Steps to reproduce
Seems to be happening if mattermost is using a top level domain (no www, no subdomains)
Expected behavior
Gitlab SSO works
Observed behavior
Gitlab SSO shows {"status": "ok"}
Possible fixes
I have debugged my problem down to this line:
https://github.com/joeferraro/react-native-cookies/blob/master/ios/RNCookieManagerIOS/RNCookieManagerIOS.m#L137
currentCookie.domain has "mydomain.ru", and topLevelDomain has ".mydomain.ru" with a dot in front.
If I add a dot to currentCookie.domain, like this it starts to work without any problems:
The text was updated successfully, but these errors were encountered: