-
Notifications
You must be signed in to change notification settings - Fork 7
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
Bump devise_saml_authenticatable from 1.5.0 to 1.6.1 to 1.6.2 #1761
Bump devise_saml_authenticatable from 1.5.0 to 1.6.1 to 1.6.2 #1761
Conversation
See my comments on the previous update for this dependancy: #1584 |
c49ee64
to
434afd3
Compare
Bumps [devise_saml_authenticatable]() from 1.5.0 to 1.6.1. Signed-off-by: dependabot-preview[bot] <[email protected]>
434afd3
to
47c6d26
Compare
A newer version of devise_saml_authenticatable exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
Gemfile.lock
Outdated
@@ -181,7 +181,7 @@ GEM | |||
railties (>= 4.1.0) | |||
responders | |||
warden (~> 1.2.3) | |||
devise_saml_authenticatable (1.5.0) | |||
devise_saml_authenticatable (1.6.1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, it might be worth bumping this to 1.6.2 - it's a reversion for a bug introduced in 1.6.1
Summary of changes
After discussion with developer, he agreed that the update did not handle instances like ours where the user model was named anything other than user. To get over this, I created a method
#current_user
on theSamlSessionsController
which returns the current provider.Also, disabled the devise
session_index_key
configuration setting, as it now expects to find a method of the specified name on the Provider model.See issue raised with developer: apokalipto/devise_saml_authenticatable#183
Bumps devise_saml_authenticatable from 1.5.0 to 1.6.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard: