Projects tagged ‘authentication’, ‘authorization’, and ‘php’

The Open Web SSO project provides core identity services to simplify the implementation of transparent single sign-on as a security component in a network infrastructure. It provides the foundation ... [More] for integrating diverse web applications that might typically operate against a disparate set of identity repositories and are hosted on a variety of platforms such as web and application servers. [Less]

A PHP implementation of SAML 2.0 service provider and identity provider functionality. And is also compatible with Shibboleth 1.3 and 2.0.

This is a module for Snappad that allows you to quickly and easily lock down your website.

It is a community created to help develop components that help define and move common digital identities throughout the computing world. Currently the main focus is on defining a common identity frame ... [More] work, provide authentication and credential caching, enable common roles and authorization, and ensure compliance via common record collecting. [Less]

With wikiplex, you can let users create their own dokuwiki namespace and setup access control. wikiplex is integrated with DokuWiki and simpleSAMLphp. NOTE: This project is in an early stage! It ... [More] is not yet documented. If you need more information or have questions, contact Andreas Åkre Solberg [Less]

PHProtect is a content protection system coded in PHP. PHProtect works under GNU/Linux, FreeBSD, OpenBSD, NetBSD, OSX, Solaris and NT/2K, they must have a CGI PHP Interpreter or Module installed on ... [More] the webserver or it won't work, it is "PHProtect", note the PHP . This program will allow you to protect a single web file whether it be PHP, HTML or ASP without having to use .htaccess. Authentication is done by a form which pulls a username and password (EG: PHP with the password ASP) from a configuration file, and if it matches what a user has submitted then it will display the content. You are probably wondering, well why can't users just access the protected file from a directory if they are smart enough to know what it's filename is?, the answer to that is simple using special code it will stop direct access to the file unless someone logs in properly on the login form, that's protection at it's best. An added feature is the ability to retrieve your username/password via a script, if you don't have access to the configuration file. PHProtect also supports the ability to use a MySQL Server for authentication, however it only connects to the server. Future releases will support the ability to change the password using a webform and store usernames and passwords in a MySQL Database. [Less]

Openpasl seeks to deliver a set of clean, simple, and loosely-coupled libraries that don't require developers to build their applications around some bloated, all things to all people, framework. ... [More] Openpasl is not an MVC framework. Some day openpasl may include several MVC models that can be used for quickly building out applications targeted at the web GTK or other presentation layers. However, this is not an explicit goal. There are common needs for applications and there are patterns of repeated tasks. The goal of openpasl is to take on some of the common architectural pieces and get them out of the way so that you can focus on the overall architecture of your application and the business logic behind it. openpasl is unstableThe current set of proposed layers to target: Database: Database "abstraction". The goal is to create a lightweight packaging system for custom/raw database drivers, with the option to use PEAR::MDB2 as a generic, portable driver. It would be encouraged to use the native PHP driver for your db backend. Simple interfaces will allow developers to wrap PHP raw driver calls within a driver class. Authentication: Implement basic layers for authentication with additional driver support (ldap, radius, mysql, saml, etc). Authorization: Implement robust RBAC library to support very granular management of permissions. Workflow: Implement generic workflow engine(s) to support the rapid deployment of transactional processes. Web: Basic web libraries to support the deployment of web services with support of various protocols (Initially SOAP and REST). Basic libraries to support dynamic page creation, HTML templates, XML, schema, XSL template controls, code templates, etc. Threading: While it is possible to do some pretty robust threading in PHP, it's also a massively huge pain in the ass - with pitfalls at every corner. Openpasl will simplify this effort into a nice package. IPC: Inter-process communication, like threading, is almost a science of its own in PHP. Openpasl seeks to abstract much of the craziness away and provide a nice clean API for IPC through shared memory and sockets. Interpreters: Interpret a language (such as JavaScript) to be ran inside of PHP in a self-contained environment. Why openpasl? Well, not all PHP applications target the web browser directly. Perhaps you're writing a socket server and threading is important to you, perhaps you're writing a data portability layer, a web service, etc. Openpasl will not force you to use any architectural style for good or for worse. Openpasl will not pollute the global scope. Openpasl gets out of the way to allow you to make the decisions you need for your application and provides you the means to perform tasks that you're really not interested in becoming an expert on (ie threading and IPC in PHP). Openpasl wants to grow! Any additional library support is welcome. The one requirement. Keep it lean. Keep it light. Use proper assignment of responsibility. Keep things loosely-coupled. PHP version?If you're pulling from the repository openpasl runs on PHP 5.3 [Less]

A repository for new ideas and experiements in the form of SimpleSAMLphp modules. These may or may not be included as part of the simpleSAMLphp repository in the future.