<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Wren Security</title>
    <description>The latest articles on DEV Community by Wren Security (@wrensecurity).</description>
    <link>https://dev.to/wrensecurity</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F7585%2F09f42906-2960-4ea0-afa7-55c55ef36c05.jpg</url>
      <title>DEV Community: Wren Security</title>
      <link>https://dev.to/wrensecurity</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wrensecurity"/>
    <language>en</language>
    <item>
      <title>Identity Synchronization With Wren:IDM</title>
      <dc:creator>Michal Marek</dc:creator>
      <pubDate>Wed, 29 Nov 2023 13:38:30 +0000</pubDate>
      <link>https://dev.to/wrensecurity/identity-synchronization-with-wrenidm-28g3</link>
      <guid>https://dev.to/wrensecurity/identity-synchronization-with-wrenidm-28g3</guid>
      <description>&lt;p&gt;Wren:IDM is an Identity Governance and Administration (IGA) platform designed to efficiently manage user accounts, access rights, and permissions within an organization. Unlike certain opinionated solutions, its flexible data model can adapt to the organizational structure and integrate naturally with established processes.&lt;/p&gt;

&lt;p&gt;In this article, we will explore provisioning, which is a crucial feature of identity management systems. Employing a CSV file as a source system. Leveraging implicit synchronization settings of Wren:IDM, any modifications will be automatically propagated to an LDAP directory.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start by cloning the Wren:IDM cookbook with Docker and Git being the prerequisites for this example: 
&lt;a href="https://github.com/WrenSecurity/wrenidm-cookbook"&gt;https://github.com/WrenSecurity/wrenidm-cookbook&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Navigate to the ‘sync’ sample folder, and spin up the prepared Docker containers using:&lt;br&gt;
&lt;/p&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;docker compose up -d
&lt;/code&gt;&lt;/pre&gt;

&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Explore the admin user interface at: &lt;a href="https://localhost:8443/admin"&gt;https://localhost:8443/admin&lt;/a&gt;.&lt;br&gt;
Log in using 'openidm-admin' as both the username and password.&lt;br&gt;
Navigate to the 'User' tab under the 'Manage' section to verify the absence of the user data that have yet to be imported.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In a typical scenario, the reconciliation process is initiated by a scheduler, but for simplicity we’ll execute it manually:&lt;br&gt;
&lt;/p&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl -k \
  -u openidm-admin:openidm-admin \
  -XPOST \
  "https://localhost:8443/openidm/recon?        
_action=recon&amp;amp;mapping=csvEmployee_managedUser"
&lt;/code&gt;&lt;/pre&gt;

&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In the Wren:IDM admin user interface, refresh the user management page to confirm the existence of new managed user identities under 'Manage' → 'User'&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;In our case Wren:IDM is configured to automatically propagate changes to LDAP. Ensure the synchronization by listing existing LDAP accounts using this command:&lt;br&gt;
&lt;/p&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;docker exec ldap ldapsearch -H ldap://localhost -x -D             
"cn=admin,dc=wrensecurity,dc=org" -w admin -b 
"dc=wrensecurity,dc=org" "(objectClass=inetOrgPerson)"
&lt;/code&gt;&lt;/pre&gt;

&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;When you’re done, feel free to continue exploring or remove the Docker containers using:&lt;br&gt;
&lt;/p&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;docker-compose stop &amp;amp;&amp;amp; docker-compose rm -f
&lt;/code&gt;&lt;/pre&gt;

&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Onboarding, layoffs and employee changes do not pose any challenges. Automatic synchronization ensures seamless, automated propagation of changes between systems without the need for manual intervention.&lt;/p&gt;

&lt;p&gt;For more information regarding synchronization, its types, mappings, scenarios, and actions, we advise reviewing our &lt;a href="https://docs.wrensecurity.org/wrenidm/latest/components/sync.html"&gt;documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Well, that is pretty sweet, but who is it for?&lt;/p&gt;

&lt;p&gt;Automation of the identity lifecycle is beneficial for all medium to large businesses. However, it is indispensable for companies with a high number of IT systems, a complicated structure, a large number of employees, high fluctuation, or regulated environments. Banks, universities, healthcare organizations, telecommunication companies, technology firms, and even public organizations. It ensures that the right people have the right access, while maintaining security standards and freeing up the hands of operations staff.&lt;/p&gt;

&lt;p&gt;If you enjoyed this article, we'd be delighted if you tried other recipes from our cookbook or explore other &lt;a href="https://wrensecurity.org"&gt;Wren Security tools&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>wrensecurity</category>
      <category>opensource</category>
      <category>identitymanagement</category>
    </item>
  </channel>
</rss>
