In this session, Tyler Gelinas, senior integration software engineer demonstrated setting up environment for ForgeRock Identity platform, developing a custom node, installing the node and dived into setting up a user login journey with the custom authentication node.
4 Likes
Nice session ! It is very helpful for beginners who wants to develop custom nodes.
2 Likes
Thank you for letting us know. If you haven’t already, please consider giving us your feedback via this form to help us deliver more such useful content for the community.
This session in packed with information on topics such as:
- how to add SmtpBaseConfig like this public interface Config extends SmtpBaseConfig
- how to migrate from 6.5 "sent email node " to 7.3.0
- how to update the shared state?
- how to update an identity once it’s added to the shared state? Example, if you want to store the latest version of the demo-node into a field in the identity.
Here are some useful resources shared by Tyler in the session:
Prerequisites:
- Experience with Trees/Journeys: ForgeRock documentation
- Custom Auth Node development guide
- Experience with java development
- Development environment - IDEs such as IntelliJ, Eclipse
Setting up environment
- Environment types
- Ensure development environment is set up
- Development preparation documentation
- Java
- Maven and maven settings
Development of a custom node
-
Nodes can be developed locally in the development environment
-
Run the mvn archetype command to get started with a template node
-
Trust Network recommendations for best practices: Marketplace Cloud Node Design documentation
Installing a node and updating a node
- Installing a node
- To compile a node, run mvn clean install
- Copy the jar file into the /WEB-INF/lib directory.
- Restart AM and the node will show up in the journey palette
- Updating a node
- Updating a node documentation
- Modify update function
- Update node version in pom.xml and plugin.java file
Delivering nodes into ForgeRock Identity Cloud
- Trust Network team can assist in delivering nodes to ForgeRock Identity Cloud
- Requests made through Technology Partner, customer field team
- Ensure the code is uploaded to github under the ForgeRock organization
- Ensure best practices are being followed, including information from the Marketplace Cloud Node Design documentation
- Open source repositories as examples
If you found this session useful, please give us feedback to help us deliver helpful content.
1 Like