getsentry/sentry - 0 views
mailgun/oxy - 0 views
httphandlers - GoDoc - 1 views
zaphar / go-html-transform - Bitbucket - 0 views
OpenAM Administration Guide - 0 views
-
An authentication service confirms the identity of a user or a client application.
-
OpenAM is most frequently used to protect web-accessible resources. Users browse to a protected web application page. An agent installed on the server with the web application redirects the user to OpenAM for access management. OpenAM determines who the user is, and whether the user has the right to access the protected page. OpenAM then redirects the user back to the protected page, with authorization credentials that can be verified by the agent. The agent allows OpenAM authorized users access the page.
Getting Started With OpenAM - 0 views
-
OpenAM centralizes authentication by using a variety of authentication modules. Authentication modules connect to identity repositories that store identities and provide authentication services. The identity repositories can be implemented as LDAP directories, relational databases, RADIUS, Windows authentication, one-time password services, other standards-based access management systems and much more.
-
OpenAM centralizes authorization by letting you use OpenAM to manage access policies separate from applications and resources. Instead of building access policy into a web application, you install a policy agent with the web application to request policy decisions from OpenAM. This way you can avoid issues that could arise when developers must embed policy decisions into their applications. With OpenAM, if policy changes or an issue is found after the application is deployed, you have only to change the policy definition in OpenAM, not deploy a new version of the application. OpenAM makes the authorization decisions, and policy agents enforce the decisions on OpenAM's behalf.
-
"OpenAM centralizes authentication by using a variety of authentication modules. Authentication modules connect to identity repositories that store identities and provide authentication services. The identity repositories can be implemented as LDAP directories, relational databases, RADIUS, Windows authentication, one-time password services, other standards-based access management systems and much more."
Running Secured Docker Registry 2.0 - Container Solutions - 0 views
-
"The new Docker Registry 2.0 was released on April 16th, 2015. It was completely rewritten in Go with added support for the new Docker Registry HTTP API V2 (thus only working with Docker 1.6+), promising to provide faster and more secure distribution of images. If you work with Docker and for some reason decided not to use the public Docker Hub, a private Docker Registry is an essential part of your architecture. But even if you don't have private images, you will likely need to use your own registry in production/testing for efficiency. The default installation, however, runs without encryption and authentication. I was wondering what's involved in securing it. There is an official tutorial on how to configure TLS on a registry server. TLS/SSL is absolutely necessary for any secure setup, but I also wanted to enable an authentication mechanism. The Configuration Reference document describes two authentication options supported by Docker Registry itself: so-called silly and token solutions. The silly one is apparently only useful for very limited development use-cases. The token solution seems to be more serious, but because of the lack of documentation (at the time of writing), I decided to find an alternative approach to secure it. In this article I'm going to show you how to set up the Docker Registry 2.0 with username/password authentication and SSL using the official Docker Registry image and a custom configured nginx as a proxy server."
Automating Docker Logging: ElasticSearch, Logstash, Kibana, and Logspout | I care, I sh... - 0 views
OAuth 2 Simplified - Aaron Parecki - 0 views
User-Managed Access (UMA) Profile of OAuth 2.0 - 0 views
OpenID Connect in a nutshell - 1 views
Joyent Triton™ - 0 views
-
"Joyent Triton™ is designed from the ground up to radically simplify container deployments in production, at scale, while delivering enterprise-grade security, software-defined networking, and bare-metal performance. Deploy Triton Elastic Container Infrastructure in your datacenter or leverage the Triton Elastic Container Infrastructure Service in the Joyent Public Cloud."
LiMux - Wikipedia, the free encyclopedia - 0 views
-
"LiMux - The IT evolution is a project by the city of Munich (third-largest city in Germany) to migrate their software systems from closed-source, proprietary Microsoft products to free and open-source software. The project was successfully completed in late 2013, which involved migrating 15,000 personal computers and laptops of public employees to free and open-source software."
Munich sheds light on the cost of dropping Linux and returning to Windows | ZDNet - 1 views
Microservices Tips and Tricks - 1 views
-
"Microservices based architectures are not new but are suddenly in the spotlight due to their powerful and sophisticated practices enabling streamlined application development and deployment. However, transitioning from a monolithic approach to a microservices-based architecture requires not only technical expertise, but organizational buy-in as well. In a recent ActiveState webinar, John Wetherill and Phil Whelan discussed a number of tips and tricks to help companies transition to and get the most out a microservices-based approach."
hooklift/gowsdl - 1 views
« First
‹ Previous
461 - 480 of 1478
Next ›
Last »
Showing 20▼ items per page