Download all versions of enmasse JAR files with all dependencies
enmasse from group us.joshuatreesoftware (version 1.0-RC24)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC24
Last update 17. March 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL http://jts.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht-jdk1.5, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC24
Last update 17. March 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL http://jts.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht-jdk1.5, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
enmasse from group us.joshuatreesoftware (version 1.0-RC23)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC23
Last update 18. February 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL http://jts.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC23
Last update 18. February 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL http://jts.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
enmasse from group us.joshuatreesoftware (version 1.0-RC22)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC22
Last update 26. January 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL http://jts.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC22
Last update 26. January 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL http://jts.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
enmasse from group us.joshuatreesoftware (version 1.0-RC21)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC21
Last update 01. January 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC21
Last update 01. January 2013
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
enmasse from group us.joshuatreesoftware (version 1.0-RC20)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC20
Last update 24. December 2012
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC20
Last update 24. December 2012
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
enmasse from group us.joshuatreesoftware (version 1.0-RC19)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC19
Last update 16. December 2012
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC19
Last update 16. December 2012
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
enmasse from group us.joshuatreesoftware (version 1.0-RC18)
EnMasse is a web application that implements RESTful Web services to interface with Fortress/OpenLDAP. En Masse was built using established Open Source technologies including Apache CXF (web services stack), Spring Framework (glue), Maven (dependencies) and JAXB (data binding layer) and runs inside any reasonably compliant Java Servlets container. En Masse’s service access decisions are made using declarative Java EE and Spring security policy hooks that are wired to connect back to the Fortress RBAC component itself. There is a one-to-one correspondence between a Fortress API and an En Masse service. The Fortress APIs are organized into 'Managers' each implementing a specific area of functionality within the Identity and Access Management lifecycle.
Artifact enmasse
Group us.joshuatreesoftware
Version 1.0-RC18
Last update 09. December 2012
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Group us.joshuatreesoftware
Version 1.0-RC18
Last update 09. December 2012
Tags: maven using managers glue apache open component fortress lifecycle itself services servlets declarative organized enmasse that decisions container compliant binding policy each stack management jaxb reasonably connect specific hooks data made security spring rbac identity area dependencies wired built between functionality application with correspondence apis openldap into layer back established restful access interface framework masse technologies including source inside there service implements java implementing runs within
Organization not specified
URL https://joshuatreesoftware.us
License BSD
Dependencies amount 27
Dependencies fortress, commons-lang, commons-configuration, commons-collections, commons-pool, commons-logging, unboundid-ldapsdk, log4j, jasypt, jgrapht, ehcache-core, slf4j-api, slf4j-jcl, cxf-bundle, spring-context, spring-core, spring-beans, spring-oxm, spring-security-acl, spring-security-config, spring-security-web, aspectjrt, aspectjweaver, spring-dao, commons-httpclient, jackson-jaxrs, commons-beanutils,
There are maybe transitive dependencies!
Page 2 from 2 (items total 17)