MohammedRafi
New Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
SnapLogic Folder Access Check
Created by @MohammedRafi from Agilisium The purpose of this pattern pipeline is to create an API that accepts user’s Email ID as an input and returns the list of SnapLogic project folders to which the user has Read, Write and Execute (R,W,X) permissions. If the user doesn’t have full access to any of the folders in SnapLogic then the pipeline will throw an empty array list. The objective is to support administration and verify access level information for each user in order to maintain governance. The pattern consists of three pipelines: Master_SnapLogic_Folder_Access_Check This pipeline is created as Triggered task. It consumes the Email ID and triggers the child pipeline and the output will be written in JSON format. Parameters: EmailID Output Values: EmailID and Path Example: {“emailId":"mohammed.rafi@agilisium.com”,“path”:[“/DEV/projects/MohammedRafi “,”/ DEV/projects/Rafi”,“/ DEV/projects/46313-Connect”,“/ DEV/projects/Transform1.0_SPARK”,“/ DEV/projects/Snaplogic-logs”]} SnapLogic-User-Folder-Access-Check This pipeline verifies the user has read access to all the project spaces. Parameters: EmailID Output Values: The output field Path will be passed to the “Master_Snaplogic_Folder_Access_Check” pipeline Child_User_Folder_Access_Check This pipeline verifies the user has RWX access for all the project folders. Parameters: EmailId api_url set to “https://elastic.snaplogic.com/api/1/rest/public/groups” path containing the org name and project space, such as “/orgname/projectSpace” organization Output Values: The output fields Path and Email ID will be passed to the “Snaplogic_User_Folder_Access_Check” pipeline Configuration Sources: REST API call by passing Email ID as parameter Targets: REST API Response and SLDB file Snaps used: Mapper, GroupBy, PipelineExecute, FileWriter, Snaplogic List, REST Get, Unique, and Filter Downloads Master-SnapLogic-Folder-Access-Check.slp (15.1 KB) SnapLogic-User-Folder-Access-Check.slp (21.8 KB) Child_User_Folder_Access_Check.slp (19.8 KB)3.6KViews0likes0CommentsSnapLogic Group Creation and Populate with List of Users
Contributed by @MohammedRafi from Agilisium The purpose of this pattern is to automate the creation of user groups and add the list of users to the group in SnapLogic using API. This is typically useful for user and access management. Configuration The pipeline validates whether the input groups already exist in SnapLogic and if not, creates a new group and adds the list of users to the group. The output will be written to a JSON file on SLDB and, we have unconnected output view to get a response using REST calls. Output Values: It contains the following fields: statusGroup, statusUser, and name. Sources: Input JSON Message using REST API Targets: REST API response and SLDB file Snaps used: REST Get, REST Post, JSON Splitter, Router, Mapper, Unique, Union, Copy, JSON Formatter, and File Writer. Downloads Sample_Input_Message.txt (314 Bytes) slProvisioning-createGroup.slp (38.6 KB)4.5KViews0likes1CommentSnapLogic User and Folder Creation
Contributed by @MohammedRafi from Agilisium The purpose of this pattern pipeline is to create a single/group of admin users and the default project folder for each user in SnapLogic using an API. Note: This pattern assumes the email convention of firstname.lastname@company.com is used. This pattern consists of two pipelines: Master_UserProvisioning.slp slProvisioning-createUser.slp Configuration Master_UserProvisioning.slp Sources: JSON File Targets: JSON File Snaps used: Mapper, JSON Splitter, Pipeline Execute, Copy, JSON Formatter, File Writer This pipeline is called from a Triggered task. It consumes the input JSON message, which contains two fields: Email ID and administrator. The Email ID field contains the list of users to be added to SnapLogic while the administrator field contains either “true” or “false”, specifying whether the user is an administrator. The output will be written in file to SLDB in JSON format and we have an unconnected output view to get the response using REST calls. Output Values: It contains the following fields: statusUser, user, and email. slProvisioning-createUser.slp Sources: email address Targets: SnapLogic user and user project Snaps used: REST Get, Mapper, Router, REST Post, Union This pipeline validates whether the users already exist in SnapLogic and if not, creates a new user and default folder in SnapLogic using REST POST. It also captures the error and sends back the response to the master user provisioning pipeline. Downloads Sample_Input_Message.txt (148 Bytes) Master_UserProvisioning.slp (12.1 KB) slProvisioning-createUser.slp (17.5 KB)