<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/discussions/f/administration/38019/saml-dynamic-attribute-mapping</link><description>Hi, 
 We have configured SAML login in our environment but we are having trouble mapping the email attribute. Our client has two types of SAML users: 
 
 internal who have their email defined in the email claim. 
 external who do not have any value defined</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143067?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2024 07:36:11 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:657e73f9-8f1c-4f4d-b1fc-6712b007716b</guid><dc:creator>Patricia</dc:creator><description>&lt;p&gt;&lt;a href="/members/naveenkumarr7411"&gt;naveenkumar11800&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t have a middleware layer between the IDP and Appian, so the second option wouldn&amp;#39;t be valid for us. I&amp;#39;ll check with my team and the IDP to see if we can get two metadata files for the configuration, as Stefan mentioned, or apply the logic you mention in the IDP&amp;nbsp;itself.&lt;br /&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143066?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2024 07:26:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:775f9fdc-15bf-47d5-862d-f552b534fbbb</guid><dc:creator>Patricia</dc:creator><description>&lt;p&gt;We are trying to figure out if we can do this directly in Appian as it will be the easiest and quickest for us while we review this issue with the IDP.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143065?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2024 07:20:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7efcbf49-c7e3-45ee-b795-eb2dfac128c3</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;Sure, you will need two of these.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143063?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2024 07:13:30 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0f082c7d-c414-486d-aaeb-71d542ea1471</guid><dc:creator>Patricia</dc:creator><description>&lt;p&gt;I have tried this already but Appian doesn&amp;#39;t allow to use the same Idp metadata file in two different confgurations. I get this error &lt;em&gt;&amp;quot;Another identity provider already exists with the same entity ID provided in this metadata file. Entity IDs must be unique.&amp;quot;&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143033?ContentTypeID=1</link><pubDate>Sat, 23 Nov 2024 14:53:05 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:45eb1099-c9a8-46c2-88c9-5412a3a56d49</guid><dc:creator>naveenkumar11800</dc:creator><description>&lt;p&gt;&amp;nbsp;&lt;a href="/members/patriciad0003"&gt;Patricia&lt;/a&gt;&amp;nbsp; and&amp;nbsp;&lt;a href="/members/stefanhelzle0001"&gt;Stefan Helzle&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Stefan&amp;rsquo;s suggestion about creating separate configurations is a great starting point! If that&amp;rsquo;s not feasible, here are a couple of other ideas:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rule-Based Mapping at the IdP:&lt;/strong&gt;&lt;br /&gt;If your IdP supports conditional logic, you could configure it to check if the &lt;code&gt;email&lt;/code&gt; claim is empty. If so, fallback to using the &lt;code&gt;name&lt;/code&gt; claim for the email attribute before sending it to Appian.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Middleware Preprocessing:&lt;/strong&gt;&lt;br /&gt;If you have a middleware layer between the IdP and Appian, it could inspect the SAML assertion and adjust the claims dynamically (e.g., map &lt;code&gt;name&lt;/code&gt; to &lt;code&gt;email&lt;/code&gt; when the &lt;code&gt;email&lt;/code&gt; claim is empty).&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143022?ContentTypeID=1</link><pubDate>Fri, 22 Nov 2024 14:32:14 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:23aff685-c7eb-4ff2-bfda-075a5483e582</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;Did you consider to create two separate configurations to the same IDP but with different mappings? When putting the two user groups into different Appian groups you can make them automatically use their respective login.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SAML Dynamic Attribute Mapping</title><link>https://community.appian.com/thread/143018?ContentTypeID=1</link><pubDate>Fri, 22 Nov 2024 12:00:37 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:22d5aa9c-2941-4a8a-88f6-cf726d3a5ef5</guid><dc:creator>David Jimenez </dc:creator><description>&lt;p&gt;Could&amp;#39;nt be possible map that value in another way?&amp;nbsp; I mean, apply that logic on the client side.,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>