<?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/"><channel><title>KB-1901 SAML authentication results in 401 caused by "Message was rejected because it was issued in the future" errors</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1901 SAML authentication results in 401 caused by "Message was rejected because it was issued in the future" errors</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors</link><pubDate>Wed, 01 Jul 2020 05:36:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/1/2020 5:36:36 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on&amp;nbsp;SAML Identity Provider (IdP)&amp;nbsp;server and the server hosting the Appian application server. The following error message is also observed in the application server log:&lt;/p&gt;
&lt;pre&gt;ERROR com.appiancorp.security.auth.saml.SamlTestServlet - Error occurred during SAML authentication test: SAML Message context failed message handler check&lt;br /&gt;com.appiancorp.security.auth.saml.exception.SecurityPolicyViolatedException: SAML Message context failed message handler check&lt;br /&gt;...&lt;br /&gt;Caused by: org.opensaml.messaging.handler.MessageHandlerException: Message was rejected because it was issued in the future&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process (IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: June 2020&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, 401, message rejected, authentication, issued in the future&lt;/div&gt;
</description></item><item><title>KB-1901 SAML authentication results in 401 caused by "Message was rejected because it was issued in the future" errors</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/14</link><pubDate>Wed, 01 Jul 2020 05:35:52 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 7/1/2020 5:35:52 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on&amp;nbsp;SAML Identity Provider (IdP)&amp;nbsp;server and the server hosting the Appian application server. The following error message is also observed in the application server log:&lt;/p&gt;
&lt;pre&gt;ERROR com.appiancorp.security.auth.saml.SamlTestServlet - Error occurred during SAML authentication test: SAML Message context failed message handler check&lt;br /&gt;com.appiancorp.security.auth.saml.exception.SecurityPolicyViolatedException: SAML Message context failed message handler check&lt;br /&gt;...&lt;br /&gt;Caused by: org.opensaml.messaging.handler.MessageHandlerException: Message was rejected because it was issued in the future&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process (IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: June 2020&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, 401, message rejected, authentication&lt;/div&gt;
</description></item><item><title>KB-1901 SAML authentication results in 401 caused by "Message was rejected because it was issued in the future" errors</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/13</link><pubDate>Wed, 01 Jul 2020 05:33:42 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 7/1/2020 5:33:42 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on&amp;nbsp;SAML Identity Provider (IdP)&amp;nbsp;server and the server hosting the Appian application server. The following error message is also observed in the application server log:&lt;/p&gt;
&lt;pre&gt;ERROR com.appiancorp.security.auth.saml.SamlTestServlet - Error occurred during SAML authentication test: SAML Message context failed message handler check&lt;br /&gt;com.appiancorp.security.auth.saml.exception.SecurityPolicyViolatedException: SAML Message context failed message handler check&lt;br /&gt;...&lt;br /&gt;Caused by: org.opensaml.messaging.handler.MessageHandlerException: Message was rejected because it was issued in the future&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process (IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: June 2020&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, 401, authentication&lt;/div&gt;
</description></item><item><title>KB-1901 SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/12</link><pubDate>Thu, 04 Jun 2020 07:01:37 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 6/4/2020 7:01:37 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on&amp;nbsp;SAML Identity Provider (IdP)&amp;nbsp;server and the server hosting the Appian application server. The following error message is also observed in the application server log:&lt;/p&gt;
&lt;pre&gt;ERROR com.appiancorp.security.auth.saml.SamlTestServlet - Error occurred during SAML authentication test: SAML Message context failed message handler check&lt;br /&gt;com.appiancorp.security.auth.saml.exception.SecurityPolicyViolatedException: SAML Message context failed message handler check&lt;br /&gt;...&lt;br /&gt;Caused by: org.opensaml.messaging.handler.MessageHandlerException: Message was rejected because it was issued in the future&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process (IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: June 2020&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, 401, authentication&lt;/div&gt;
</description></item><item><title>KB-1901 SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/11</link><pubDate>Thu, 04 Jun 2020 07:01:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 6/4/2020 7:01:17 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on&amp;nbsp;SAML Identity Provider (IdP)&amp;nbsp;server and the server hosting the Appian application server. The following error message is also observed in the application server log:&lt;/p&gt;
&lt;pre&gt;ERROR com.appiancorp.security.auth.saml.SamlTestServlet - Error occurred during SAML authentication test: SAML Message context failed message handler check&lt;br /&gt;com.appiancorp.security.auth.saml.exception.SecurityPolicyViolatedException: SAML Message context failed message handler check&lt;br /&gt;...&lt;br /&gt;Caused by: org.opensaml.messaging.handler.MessageHandlerException: Message was rejected because it was issued in the future&lt;/pre&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process(IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed: June 2020&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, 401, authentication&lt;/div&gt;
</description></item><item><title>KB-1901 SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/10</link><pubDate>Thu, 28 Mar 2019 14:46:49 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Jordan Horwat</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 3/28/2019 2:46:49 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on&amp;nbsp;SAML Identity Provider (IdP)&amp;nbsp;server and the server hosting the Appian application server.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process(IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/9</link><pubDate>Fri, 15 Mar 2019 09:55:59 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 9 posted to Appian Knowledge Base by Tejas Kargutkar on 3/15/2019 9:55:59 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on IdP server and the server hosting the Appian application server.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process(IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/8</link><pubDate>Fri, 15 Mar 2019 09:55:15 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 8 posted to Appian Knowledge Base by Tejas Kargutkar on 3/15/2019 9:55:15 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on IdP server and the server hosting Appian.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process(IdP Server, Appian application server) are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/7</link><pubDate>Fri, 15 Mar 2019 09:50:27 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 3/15/2019 9:50:27 AM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;There is a mismatch in the server time on IdP server and the server hosting Appian.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;When the SAML Identity Provider authorizes the token, it is dated with the exact time and date when it was sent to Appian.&amp;nbsp;When Appian receives this request, it rejects the token considering the request being sent in the past or the future depending on the mismatch of the server time.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/6</link><pubDate>Thu, 14 Mar 2019 16:00:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Jordan Horwat</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 3/14/2019 4:00:38 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may&amp;nbsp;occur when a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response. For example,&amp;nbsp;there is a mismatch between the server time on IdP server and the server hosting Appian.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>SSO authentication results in a 401 due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/1</link><pubDate>Fri, 08 Mar 2019 17:33:31 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 3/8/2019 5:33:31 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&lt;/p&gt;
&lt;p&gt;Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;The authentication attempt in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt; is logged as &lt;strong&gt;FAILED&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;SAML response&amp;nbsp;has a timestamp associated with it. This issue may happen if a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;This has been observed in cases where server hosting the Appian application has the server time off by a minute or more.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/5</link><pubDate>Fri, 08 Mar 2019 15:56:04 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Jordan Horwat</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 3/8/2019 3:56:04 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&amp;nbsp;The SAML authentication attempt is logged as FAILED in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt;&amp;nbsp;file. However, Appian authentication works as expected.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may happen if a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;This has been observed in cases where server hosting the Appian application has the server time off by a minute or more.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SAML authentication results in a 401 error due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/4</link><pubDate>Fri, 08 Mar 2019 12:42:25 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 3/8/2019 12:42:25 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&lt;/p&gt;
&lt;p&gt;Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;The authentication attempt in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt; is logged as &lt;strong&gt;FAILED&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may happen if a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;This has been observed in cases where server hosting the Appian application has the server time off by a minute or more.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>DRAFT KB-XXXX SSO authentication results in a 401 due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/3</link><pubDate>Fri, 08 Mar 2019 12:39:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 3/8/2019 12:39:38 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&lt;/p&gt;
&lt;p&gt;Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;The authentication attempt in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt; is logged as &lt;strong&gt;FAILED&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may happen if a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;This has been observed in cases where server hosting the Appian application has the server time off by a minute or more.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item><item><title>SSO authentication results in a 401 due to wrong server time</title><link>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors/revision/2</link><pubDate>Fri, 08 Mar 2019 12:35:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c66d59b6-5be3-48cb-8318-290c8962515f</guid><dc:creator>Tejas Kargutkar</dc:creator><comments>https://community.appian.com/support/w/kb/1372/kb-1901-saml-authentication-results-in-401-caused-by-message-was-rejected-because-it-was-issued-in-the-future-errors#comments</comments><description>Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 3/8/2019 12:35:17 PM&lt;br /&gt;
&lt;h2&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;SAML&amp;nbsp;authentication&amp;nbsp;results in a 401 error for all users.&lt;/p&gt;
&lt;p&gt;Appian authentication works as expected.&lt;/p&gt;
&lt;p&gt;The authentication attempt in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/logs/login-audit.csv&lt;/code&gt; is logged as &lt;strong&gt;FAILED&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;Cause&lt;/h2&gt;
&lt;p&gt;This issue may happen if a wrong date or time is set on the servers involved in the authentication process, which will invalidate the SAML request/response.&lt;/p&gt;
&lt;p&gt;This has been observed in cases where server hosting the Appian application has the server time off by a minute or more.&lt;/p&gt;
&lt;h2&gt;Action&lt;/h2&gt;
&lt;p&gt;Ensure that the servers involved in the authentication process are configured with the correct time.&lt;/p&gt;
&lt;h2&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;div class="content"&gt;
&lt;div class="content"&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;March 2019&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: SAML, integration, authentication&lt;/div&gt;
</description></item></channel></rss>