-
Notifications
You must be signed in to change notification settings - Fork 11k
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
SAML broken after recent update #10056
Comments
+1, was working on 0.61.0 with Microsoft ADFS.. Now it's not |
+1
That particular file hasn't changed I believe for last few releases , but under lying package could be causing this. |
Working with SimpleSamlPHP I could reproduce that. I had to Change 2 Spots in steffo_meteor-accounts-saml.js to get it working:
and
see those '.value' I had to append to make it work. |
+1 We're seeing this as well on 0.62.1 |
@rodrigok can you have a look into this one? |
+1, SAML with Auth0 is not working for me either |
Is there any progress with this issue? It looks like the pull request needs a review. I've also discovered that manually editing a snap is an absolute pain, and downgrading to the previous rocket chat version likes to spew out database schema errors making this a very inconvenient and disruptive breakage. |
We can not confirm that 0.62.2 has broken SAML after an upgrade 5 days ago yet (maybe all tokens are still alive). We are using NodeJS v8.9.3, though. |
@inksis sorry, we use oauth (with keycloak), which still works. I mixed up the SSO method, sorry for the confusion. But I was told by @arminfelder that he improved the parsing in the SAML meteor library. So better look there instead of patching here. |
Any idea when this will be pushed and a new version released? We are waiting to deploy RocketChat, but can't without SAML working. |
@pageb018 just created a pull request #10209, which fixes the issue in a clean way, |
@arminfelder I deploy via docker-compose. Not sure if I can use your hot fix that way. Is it in a docker repository? |
@pageb018 no its not, just take the Dockerfile from .docker/Dockerfile, place it in the same folder as the tar.gz and replace the first RUN with ADD rc0.62.2-samlhotfix.tar.gz /app/ |
@arminfelder getting closer. But the docker build fails with the following error: I am pretty new to docker, so I may be making a obvious mistake. I have both the tar and dockerfile in the same directory. |
@pageb018 you need to replace the whole first RUN block including the && curl -SLf..., I uploaded my Dockerfile: https://cloud.felder-edv.at/index.php/s/wsYK4P4a7g2MZEy |
@arminfelder thank you! Let me give it a shot. |
👍 please fix this guys, i want to use RocketChat again |
Will the fix be in .63? Or anytime soon? |
Automatic test cases are useful.
Op vr 30 mrt. 2018 18:29 schreef anicoa <notifications@github.com>:
… can not confirm that #10209
<#10209> fixes SAML login.
Had to apply changes of #10084
<#10084> (append .value two
times) which "solved" the problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10056 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACEWNK5f0pPpwycGPotbb4FsxP3BXcjFks5tjl1agaJpZM4SiFuw>
.
|
@ChessSpider fully agree |
@arminfelder I had a few issues running the docker file you sent over, then I got pulled to a different project. Plan is jump back in on Monday. I will post the error I am getting, I am sure it's my lack of docker knowledge. |
@arminfelder you are right, sorry. First checked only last modified timestamp of files which showed me the changes; checking the files' content showed me that the pr wasn't applied. will try again later and report... |
@arminfelder I applied #10210 to branch develop configured saml and now I get the following error: TypeError: values is not iterable; if i change in line 430 in saml_utils.js the
it seems to work as expected. |
@anicoa thx for checking, I replaced the for of with a regular for loop |
soooo..... im surprised this hasn't been fixed yet. I predict a riot. |
This is breaking for me. If anyone has a guide on implementing the fixes to a snap, I would be grateful. I'm happy to help and experienced with coding, just new to snaps. (Running 0.62.2, 1239 candidate) |
@profrowe I haven't tried, but I guess you can |
@arminfelder circling back to the dockerfile.. When I try and build, I get the following using your dockerfile.
|
@pageb018 thas does not look like my Dockerfile, where does this "&& curl -SLf "https://releases.rocke..." come from? here is mine:
|
Weird. Ok. So using the above docker file, I get the follow:
|
@pageb018 I guess its a problem with the cache, try "docker build --no-cache rocket_saml ." and obviously, the Dockerfile and the rc0.62.2-samlhotfix.tar.gz need to be in the same folder |
@arminfelder unfortunately same issue with the no cache flag. Hmm... |
+1 for this to be prioritised for the next release. |
@pageb018 it just uploaded my build to dockerhub: docker pull afelder/rocketchat:0.62.2-samlfix |
@arminfelder thank you! I am up and running again with SAML back and working perfectly. Appreciate all the help. |
Let us know if the |
Description:
A recent update to rocketchat-server 0.62.1 seems to have broken SAML.
The SAML process works correctly until the SAML token is returned back to Rocket Chat, where the below error occurs. The previous version (unsure exactly which one as snap handles updates) worked correctly.
Server Setup Information:
Relevant logs:
The text was updated successfully, but these errors were encountered: