osiam / docker-image

OSIAM Docker Image

OSIAM - Open Source Identity and Access Management

Active development of this project has stopped.

OSIAM is a secure identity management solution providing REST based services for authentication and authorization. We achieve this by implementing two important open standards:

• OAuth 2.0
• SCIM 2.0

OSIAM is published under the MIT licence, giving you the greatest freedom possible to utilize OSIAM in you project or product. Watch our blog to stay informed about releases and upcoming changes.

Use cases

• Single app with OSIAM as free backing store for users and groups and local auth service.
• Distributed app with OSIAM as central identity store and auth service.
• Publish your app's API with OSIAM as auth service for 3rd-parties and allow safe access to your user's data.

Quick Start

Download the latest version of OSIAM:

curl -L https://dl.bintray.com/osiam/downloads/osiam/3.0/osiam-3.0.war -o osiam.war

Make the .war file executable:

chmod +x osiam.war

Start OSIAM:

./osiam.war

After some seconds, OSIAM should be fully running. You can now retrieve your first access token:

curl -H "Authorization: Basic ZXhhbXBsZS1jbGllbnQ6c2VjcmV0" -X POST -d "grant_type=client_credentials&scope=ADMIN" http://localhost:8080/oauth/token

You can now start to setup OSIAM, by changing the administrator's password and add your own OAuth client. Please see the Installation and Configuration Manual for details.

Documentation

Learn how to install and configure OSIAM for production in the documentation.

Components

• osiam handles the authentication and authorization based on OAuth 2.0 and holds the SCIM based user data
• addon-self-administration provides account management self-service as a web application
• addon-administration lets you administer users and groups via a web application

Easy customization

Every visual aspect of OSIAM's components can be easily customized by supplying your own templates, stylesheets and scripts to make OSIAM integrate seamlessly with your application. Read the customization guide to learn more.

Snapshots

To use the latest snapshot of OSIAM just download it from JFrog OSS: https://oss.jfrog.org/repo/org/osiam/osiam/latest-SNAPSHOT/

Scroll down to the bottom of the page and select the latest WAR file.

Issue Tracker

Please report issues, bugs and feature requests via [the issue tracker] (https://github.com/osiam/osiam/issues).

Get involved

Help is very appreciated. Please read the contributors guide to learn how to get started.

docker-image's Issues

Flyway migration should be done like in osiam/vagrant

@tkrille already did it in osiam/vagrant. The database migration should be done with the flyway command line migration to get rid off the problem of importing the setup data of the addons if the database schema is not created already by flyway.

Remove build on Travis CI

Correlates with #13

Use Gradle instead of Maven

Now that the migration to Gradle is finished, the Docker build has to be migrated too. It still expects an OSIAM that is based on a Maven build.

Install SMTP server for testing

Maybe like @dacrome did it here: osiam/vagrant#5

Docker OSIAM image is redirecting always to localhost

Once docker is up and running, and as the instructions state, we try to go to http://192.168.99.100:8080/addon-administration (for example), in which URL the IP 192.168.99.100 is the one in which docker is running, it is automatically redirected to http://localhost:8080/osiam-auth-server/oauth/authorize?client_id=....
After that, I have to change localhost manually to the right IP, and then I am able to see the login page:

How can I solve this? Trying to dig into the configuration, to see if I can find something, but nothing yet! :/

Thanks a lot!

Build the docker image on CircleCI

Like most of the OSIAM repos, the docker image should also be tested by building the image and starting the container on CircleCI. I already created a branch with a circle file, but on circle the build has errors:

dpkg: unrecoverable fatal error, aborting: failed to fstat previous diversions file: No such file or directory E: Sub-process /usr/bin/dpkg returned an error code (2) lxc-start: The container failed to start. lxc-start: Additional information can be obtained by setting the --logfile and --logpriority options.

Does anyone knows why the build fails?

Tomcat does not log

The Tomcat running in the Docker image does not log anything from our services. That's sad, because you cannot really see errors and stuff, which is something, that a development image should provide.

Cannot build Docker image

While building Docker image with the build command, I ger this error:

[ERROR] Failed to execute goal on project osiam: Could not resolve dependencies for project org.osiam:osiam:war:3.0-SNAPSHOT: Failed to collect dependencies at org.osiam:connector4java:jar:1.8-SNAPSHOT: Failed to read artifact descriptor for org.osiam:connector4java:jar:1.8-SNAPSHOT: Could not transfer artifact org.osiam:connector4java:pom:1.8-SNAPSHOT from/to osiam snapshots repo (https://maven-repo.evolvis.org/snapshots): Not authorized , ReasonPhrase:Authorization Required.