cas-webapp-docker - Apereo CAS Server web application running inside a docker container.

  •        128

This repository hosts the Docker build configuration necessary to build a CAS image. See the Dockerfile for more info. A docker image for CAS server. Images are tagged to match CAS server releases.

https://hub.docker.com/r/apereo/cas/
https://github.com/apereo/cas-webapp-docker

Tags
Implementation
License
Platform

   




Related Projects

Apereo CAS - Enterprise Single Sign On for all earthlings and beyond

  •    Java

Welcome to the home of the Central Authentication Service project, more commonly referred to as CAS. CAS is an enterprise multilingual single sign-on solution for the web and attempts to be a comprehensive platform for your authentication and authorization needs. CAS is an open and well-documented authentication protocol. The primary implementation of the protocol is an open-source Java server component by the same name hosted here, with support for a plethora of additional authentication protocols and features.

java-cas-client - Apereo Java CAS Client

  •    Java

Jasig CAS Client for Java is the integration point for applications that want to speak with a CAS server, either via the CAS 1.0 or CAS 2.0 protocol.

Jasig CAS single sign-on server emulation with ASP.NET

  •    

This project contains code that can extent an existing ASP.NET web application to emulate the single sign-on functionality of a Jasig Central Authentication Service (CAS).

devise_cas_authenticatable - CAS authentication support for Devise

  •    Ruby

devise_cas_authenticatable is CAS single sign-on support for Devise applications. It acts as a replacement for database_authenticatable. It builds on rubycas-client and should support just about any conformant CAS server (although I have personally tested it using rubycas-server). You can also add other modules such as token_authenticatable, trackable, etc. Please do not add database_authenticatable as this module is intended to replace it.

kibana-authentication-proxy - Hosts the latest kibana3 and elasticsearch behind Google OAuth2, Basic Authentication or CAS Authentication

  •    Javascript

Hosts the latest kibana3 and elasticsearch behind Google OAuth2, Basic Authentication or CAS Authentication with NodeJS and Express. It's just a standard nodejs application, you could install it in the same server with ES, or not. Before run the following commands, please make sure you have nodejs and npm well installed.


phpCAS - Jasig PHP CAS Client

  •    PHP

phpCAS is an authentication library that allows PHP applications to easily authenticate users via a Central Authentication Service (CAS) server. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Silhouette - Authentication library for Play Framework

  •    Scala

Silhouette is an authentication library for Play Framework applications that supports several authentication methods, including OAuth1, OAuth2, OpenID, CAS, Credentials, Basic Authentication, Two Factor Authentication or custom authentication schemes.

Harbor - An enterprise-class container registry server based on Docker Distribution

  •    Go

Project Harbor is an enterprise-class registry server that stores and distributes Docker images. It extends the open source Docker Distribution by adding the functionalities usually required by an enterprise, such as security, identity and management. As an enterprise private registry, Harbor offers better performance and security.

uPortal - Enterprise open source portal built by and for the higher education community.

  •    Java

uPortal is the leading open source enterprise portal framework built by and for the higher education community. uPortal continues to evolve through contributions from its global community and is supported by resources, grants, donations, and memberships fees from academic institutions, commercial affiliates, and non-profit foundations. uPortal is built on open standards-based technologies such as Java and XML, and enables easy, standards-based integration with authentication and security infrastructures, single sign-on secure access, campus applications, web-based content, and end user customization. uPortal can easily integrate with other enterprise systems and can be customized for specific local needs. You may download uPortal and use it on your site at no cost. Unlike our competitors, uPortal is 100% free open source software managed by Apereo. Our community has access to all releases of the uPortal software with absolutely no costs. We welcome contributions from our community of all types and sizes.

CASino - CASino is a Ruby-based Single Sign-On solution supporting the CAS standard

  •    Ruby

CASino Rails Engine (used in CASinoApp). It currently supports CAS 1.0 and CAS 2.0 as well as CAS 3.1 Single Sign Out.

play-pac4j - Security library for Play framework 2 in Java and Scala: OAuth, CAS, SAML, OpenID Connect, LDAP, JWT

  •    Java

The play-pac4j project is an easy and powerful security library for Play framework v2 web applications which supports authentication and authorization, but also logout and advanced features like CSRF protection. It can work with Deadbolt. It's based on Play 2.6 (and Scala 2.11 or Scala 2.12) and on the pac4j security engine v3. It's available under the Apache 2 license. The LogoutController logs out the user from the application.

LDAP CAS plugin

  •    C

LDAP bind SLAPI plugin for CAS authentication. Plugin has been tested and is working in a real system since march 2007. It is developed for Fedora DS, and should also work with no changes or minimal ones in RedHat DS and SUN. Openldap port is in progress

cas - Jasig CAS - Single Sign On for the Web

  •    Java

Jasig CAS - Single Sign On for the Web

ESUP-Portail CAS Generic Handler

  •    

ESUP-Portail CAS Generic Handler is a plugin giving CAS the ability to authenticate users with different methods (LDAP, database, files, NIS, ...).

Docker-Secure-Deployment-Guidelines - Deployment checklist for securely deploying Docker

  •    

Within today’s growing cloud-based IT market, there is a strong demand for virtualisation technologies. Unfortunately most virtualisation solutions are not flexible enough to meet developer requirements and the overhead implied by the use of full virtualisation solutions becomes a burden on the scalability of the infrastructure. Docker reduces that overhead by allowing developers and system administrators to seamlessly deploy containers for applications and services required for business operations. However, because Docker leverages the same kernel as the host system to reduce the need for resources, containers can be exposed to significant security risks if not adequately configured. The following itemised list suggests hardening actions that can be undertaken to improve the security posture of the containers within their respective environment. It should be noted that proposed solutions only apply to deployment of Linux Docker containers on Linux-based hosts, using the most recent release of Docker at the time of this writing (1.4.0, commit 4595d4f, dating 11/12/14). Part of the content below is based on publications from Jérôme Petazzoni [1] and Daniel J Walsh [2]. This document aims at adding on to their recommendations and how they can specifically be implemented within Docker. Note: Most of suggested command line options can be stored and used in a similar manner inside a Dockerfile for automated image building. Docker 1.3 now supports cryptographic signatures [3] to ascertain the origin and integrity of official repository images. This feature is however still a work in progress as Docker will issue a warning but not prevent the image from actually running. Furthermore, it does not apply to non-official images. In general, ensure that images are only retrieved from trusted repositories and that the --insecure-registry=[] command line option is never used.

docker-cloud - Automatically run your Docker containers on Google Compute Engine

  •    Go

```Once the authorization is completed, you can start the proxy server. If you don't specify any project ID, it'll use the project ID provided during authorization.```docker-cloud start [-project=<your-google-cloud-project-here>]```

muguet - DNS Server & Reverse proxy for Docker - Compatible with docker-compose, boot2docker and docker-machine

  •    Javascript

When using Docker, it's sometimes a pain to access your containers using specific IPs/ports. Muguet provides you with a DNS Server that resolves auto-generated hostnames to your containers IPs, plus a Reverse Proxy to access all your web apps on port 80.

dockerfiles-windows - Various Dockerfiles for Windows Containers

  •    Javascript

Various Dockerfiles for Windows. Most of these can be run as Windows Containers on Windows 10, Windows Server 2016, Windows Server 1709 and Windows Server 1803. Most of these Dockerfiles are automatically built on AppVeyor and pushed to Docker Hub. See the badges in each sub folder's README files.

Weave - Simple, Resilient Multi-host Docker Networking

  •    Go

Weave is a simple, portable and reliable way to network and manage containers and microservices. It provides a simple and resilient network for your application that is portable across data centers and public clouds. Weave Net creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery.

ignite - Ignite a Firecracker microVM

  •    Go

Weave Ignite is an open source Virtual Machine (VM) manager with a container UX and built-in GitOps management. Ignite makes Firecracker easy to use by adopting its developer experience from containers. With Ignite, you pick an OCI-compliant image (Docker image) that you want to run as a VM, and then just execute ignite run instead of docker run. There’s no need to use VM-specific tools to build .vdi, .vmdk, or .qcow2 images, just do a docker build from any base image you want (e.g. ubuntu:18.04 from Docker Hub), and add your preferred contents.