In May we restarted our Tech Talk Live programme, led by architects, engineers and developers. In the first session @tpage and I presented on (Re)Indexing Large Repositories.

There were many questions and we only had time to answer a few during the session. Due to the quantity of questions we have batched them up and will try to answer them in a series of blog posts.

You can find the Part 1 of this blog post in (Re)Indexing Large Repositories - Follow up questions

In May we restarted our Tech Talk Live programme, led by architects, engineers and developers. In our first session Angel and I presented on (Re)Indexing Large Repositories.

There were many questions and we only had time to answer a few during the session. Due to the quantity of questions we have batched them up and will try to answer them in a series of blog posts. This post is the first in the series and we go through some of the easier to answer questions providing links to our documentation.

Learn how to get documents contained in a folder or in a folder hierarchy using the Alfresco REST API.

In this article we will have a look at how to use the Alfresco Identity Services for centralized authentication and single sign on (SSO) with the Alfresco Digital Business Platform (DBP).

Alfresco DBP consists of Alfresco Content Services (ACS), Alfresco Process Services (APS), Alfresco Governance Services (AGS), and a number of modules and development frameworks, such as Alfresco Application Development Framework (ADF).

The Alfresco Identity Service has been available to use since ACS 6.0, APS 1.9, and ADF 2.4 product releases. In this article we will be using the following product versions: Identity Service 1.2, ACS 6.2.1, APS 1.11 and ADF 3.8. 

This means that the applications that we are working with, such as ACS, APS, and ADF clients don’t have to deal with login forms and authentication. Once a user is logged into the Alfresco Identity Service they don’t have to login again to access ACS, APS, or any ADF application.

This also applies to logout, which means that once a user is logged out of Alfresco Identity Service they are also automatically logged out of all other applications.

Alfresco Identity Service is implemented on top of JBoss Keycloak, which is both an Identity Provider (IdP) and a token issuer for OAuth 2 tokens. Keycloak deals with authentication, safety password storage, SSO, two factor authentication etc. Keycloak supports protocols such as OpenID Connect and SAML. Keycloak can store the user data in a variety of places, such as LDAP, Active Directory, and RDBMS.

Alfresco Identity Service is basically a wrapper around the JBoss Keycloak service.

Git offers many advantages over older source control systems and has become the de facto industry standard.  However it does not offer fine-grained access controls, instead assuming that developers should have access to the whole repository or none of it.  In this post we look at how mirroring can be used to maintain a separate repository that provides public access to part of the repository, while ensuring the remainder is private.