This repository has been archived by the owner on Jul 28, 2021. It is now read-only.
Bundle update #32
Open
Bundle update #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Get up to at least the latest Ruby version with Rails 4.2 latest
It could be in a separate PR to update to Rails 5(.1), but this one has been tested by me and passed my smoke test. (I was able to set up test authenticator and log in with a test user and password matching the username.)
Thanks! This is great, my campus implements CAS and I am on the development team, but it has been an impediment to developing that I have to be on campus network at all times (and logged into VPN when I am remote.)
So I am setting up a standalone test network on which all real employee information can be replaced with fake ones. I'm going to need a CAS server, I have an API for authorization, that I will also need to be replicating into my test environment... this example CAS app with the addition of the Test authenticator driver was just what I needed! I was thinking I might reconfigure it so that users that are not known to the authorization service can't be authenticated, but I don't know if I even need to do that. If they don't get authorized, they won't be allowed into the application, so ...
Anyway, this is great! Just what I needed, thank you very much!
PR simply does bundle update and includes migrations and other various asset/etc file updates from the later version of the CASino gem installer.