su-sws / stanford_ssp
A Drupal Authentication Module.
Installs: 49 723
Dependents: 1
Suggesters: 0
Security: 0
Stars: 9
Watchers: 17
Forks: 8
Open Issues: 20
Type:drupal-custom-module
Requires
- php: >=8.1
- ext-json: *
- drupal/core: ^9.4 || ^10.0
- drupal/simplesamlphp_auth: ^3.1
Requires (Dev)
- su-sws/drupal-patches: ^8.0
- 8.x-dev
- 8.3.5
- 8.3.4
- 8.3.3
- 8.3.2
- 8.3.1
- 8.3.0
- 8.2.6
- 8.2.5
- 8.2.4
- 8.2.3
- 8.2.2
- 8.2.1
- 8.2.0
- 8.1.7
- 8.1.6
- 8.1.5
- 8.1.4
- 8.1.3
- 8.1.2
- 8.1.1
- 8.1.0
- 7.2.2-alpha.11
- 7.2.2-alpha.10
- 7.2.2-alpha9
- 7.2.2-alpha8
- 7.2.2-alpha7
- 7.2.2-alpha6
- 7.2.2-alpha5
- 7.2.2-alpha4
- 7.2.2-alpha3
- 7.2.2-alpha2
- 7.2.2-alpha1
- dev-main
- dev-master
- dev-7.x-2.x
- dev-SITES-993
- dev-nested-workgroups
- dev-D8CORE-1523
- dev-SITES-900
- dev-722-alpha2
- dev-SITES-616a
This package is auto-updated.
Last update: 2024-04-11 18:36:09 UTC
README
Version: 8.x-2.x
Maintainers: jbickar, sherakama, pookmish
Additional enhancements to the Drupal contrib module SimpleSamlPHP Auth. See the contrib module for more documentation.
Installation
Follow installation guide provided by SimpleSamlPHP Auth
Prerequisites
SimpleSAMLphp - you must have SimpleSAMLphp version 1.6 or newer installed and configured to operate as a service provider (SP).
See more at the documentaion for SimpleSamlPHP Auth
Configuration
The main configuration page can be found at: /admin/config/people/simplesamlphp_auth
To use the workgroup API, you must work with the MAIS team to get a valid certificate. V1 API certificates do not automatically work with the V2 API.
Troubleshooting
Send a helpsu to Stanford Web Services or post an issue to the GitHub issue queue.
Contribution / Collaboration
You are welcome to contribute functionality, bug fixes, or documentation to this module. If you would like to suggest a fix or new functionality you may add a new issue to the GitHub issue queue or you may fork this repository and submit a pull request. For more help please see GitHub's article on fork, branch, and pull requests
Releases
Steps to build a new release:
- Checkout the latest commit from the
8.x-2.xbranch. - Create a new branch for the release.
- Commit any necessary changes to the release branch.
- These may include, but are not necessarily limited to:
- Update the version in any
info.ymlfiles, including in any submodules. - Update the CHANGELOG to reflect the changes made in the new release.
- Make a PR to merge your release branch into
master - Give the PR a semver-compliant label, e.g., (
patch,minor,major). This may happen automatically via Github actions (if a labeler action is configured). - When the PR is merged to
master, a new tag will be created automatically, bumping the version by the semver label. - The github action is built from: semver-release-action, and further documentation is available there.