LDS Account Integration

Disclaimer

• This is a training NOT a presentation.– Be prepared to learn and participate in labs

• Please ask questions• Prerequisites:– Java Knowledge– Basic understanding of LDAP

History

• In the beginning Maven and CruiseControl– Produced an .ear

• Automated config and deploy Bundles– Produced a .zip with an .ear/.war and env config– DB Migrator produced a migration .zip

• Anthill Pro replaces CruiseControl– Introduced secondary process execution

What is LDS Account?

• LDS Account is meant to be the single source for user authentication and basic user information

• LDS Account is implemented with LDAP• LDS Account is an application for maintaining

user attributes

LDS Account"LDS Account is a single user name and password for any person who interacts with online LDS Church resources. LDS Account is the primary account authentication credentials for most Church sites and applications. It reduces development costs that would be incurred as the user interfaces change, or as upgrades to security and the registration process are required. Unlike previous authentication systems, LDS Account is a branded single sign-on solution that is centrally managed at ldsaccount.lds.org."

LDS Account (cont.)

"LDS Account has become the key to accessing all the resources the Church has to offer, such as family history tools, ward and stake websites, employment resources, and more. ... The idea is to have only one username and password that you can use with all password-protected websites the Church has."

User Details

• LDS Account also provides user information– User details– User details can be exposed through LDAP attributes,

or WAM headers, or SAML attributes

LDS Account integration in the Stack

• Consists of two main parts– Authentication– User information (details)

LDS Account User Details Integration

• The LDS Account module acts as a Java model for LDS Account information

• LdsAccountDetails.java is the abstraction layer for LDS Account user details integration

• Factories generate LdsAccountDetails object for each user– Factories handle the different formats in which the

raw user details attributes are provide to the application• LDAP attributes, WAM headers, SAML, …

Lab 1

https://tech.lds.org/wiki/LDS_Account_Integration_-_Part_1#Lab_1

Spring Security

Maven Lifecycles

• Maven uses lifecycles to orchestrate goals• Phases represent steps in a lifecycle

Default

process-resources

compile

test-compile

test

package

integration-test

install

deploy

Clean

pre-clean

clean

Site

site

site-deploy

Example Binding in Pom Config<project> … <packaging>war</packaging> <build> <plugins>

<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>1.0.1</version> <executions> <execution> <goals><goal>enforce</goal></goals> <phase>compile</phase> </execution> </executions> </plugin> </plugins> </build></project>

Lab 2

https://tech.lds.org/wiki/LDS_Account_Integration_-_Part_1#Lab_2

Conclusion

• LDS Account rocks!• The Stack LDS Account integration rocks!• Shamu rocks!

Credit Where Credit is Due