{"id":1291,"date":"2014-09-05T16:08:38","date_gmt":"2014-09-05T16:08:38","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=1291"},"modified":"2020-12-03T14:48:25","modified_gmt":"2020-12-03T21:48:25","slug":"single-sign-on","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/","title":{"rendered":"Single Sign On"},"content":{"rendered":"<h3><span id=\"Overview_36\" class=\"mw-headline\">Overview<\/span><\/h3>\n<p><b>Single sign-on<\/b>\u00a0(<b>SSO<\/b>) is a mechanism of\u00a0access control\u00a0that can be applied on multiple related, but independent\u00a0software\u00a0systems. With this mechanism a user\u00a0logs in\u00a0once and gains access to multiple systems without being prompted to log in again for each individual application. Conversely,\u00a0<b>single sign-off<\/b>\u00a0is property mechanism whereby a single action of signing out terminates access to multiple software systems.<\/p>\n<p>As different applications and resources support different\u00a0authentication\u00a0mechanisms, single sign-on has to internally translate to and store different credentials compared to what is used for initial authentication.<\/p>\n<p>Ephesoft Transact has been tested with the following SSO-related components:<\/p>\n<ul>\n<li><strong>SAML 2.0\u00a0<\/strong>\u2014 An XML-based protocol that entails security tokens for authentication and authorization. Ephesoft Transact supports SAML 2.0, and has tested and certified the following identity providers that are compatible with Ephesoft Transact:\n<ul>\n<li><strong>ADFS<\/strong><\/li>\n<li><strong>Okta<\/strong><\/li>\n<li><strong>PingFederate<\/strong><\/li>\n<li><strong>SSOCircle<\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"padding-left: 60px\">For additional information about configuring SAML 2.0 SSO with Ephesoft Transact, please refer to the following document:<\/p>\n<p style=\"padding-left: 90px\"><a href=\"https:\/\/ephesoft.com\/docs\/configurations\/user-connectivity\/configuring-saml-sso\/\">Manually Configuring SAML 2.0 SSO for Ephesoft Transact 4.5.0.x<\/a><\/p>\n<ul>\n<li><strong>CAS-based SSO Framework<\/strong> \u2014 CAS is an Enterprise Java solution for web application authentication that also provides the benefit of Single Sign-On (SSO).<\/li>\n<\/ul>\n<p style=\"padding-left: 60px\">For additional information about CAS-based SSO with Ephesoft Transact, please refer to the following document:<\/p>\n<p style=\"padding-left: 90px\"><a href=\"https:\/\/ephesoft.com\/docs\/configurations\/user-connectivity\/sso-cas-based-sso-framework\/\">SSO | CAS-Based SSO Framework<\/a><\/p>\n<ul>\n<li><strong>Transport Layer Security (TLS)<\/strong> \u2014 Ephesoft Transact 4.5.0.x supports TLS versions 1.0, 1.1 and 1.2.<\/li>\n<\/ul>\n<h3><span id=\"Benefits\" class=\"mw-headline\">Benefits<\/span><\/h3>\n<ol>\n<li>Reducing\u00a0password fatigue\u00a0from different user name and password combinations.<\/li>\n<li>Reducing time spent re-entering passwords for the same identity.<\/li>\n<li>Reduced Logins For Discreet Systems\n<ol>\n<li>Corporate Systems<\/li>\n<li>Shared Intranet\/Web Applications<\/li>\n<li>Web Logon Aggregators<\/li>\n<\/ol>\n<\/li>\n<li>Reduced cost to reset a password<\/li>\n<li>Reduced time spent logging into multiple systems each time<\/li>\n<li>Reduces multiple authentication, unnecessary user clicks, forgotten passwords, multiple profiles.<\/li>\n<li>Limited time and resources to develop IT solutions.<\/li>\n<\/ol>\n<h3><span id=\"Criticisms\" class=\"mw-headline\">Challenges<\/span><\/h3>\n<ol>\n<li>As single sign-on can provide access to many resources\/systems at once using a single credential (&#8220;keys to the castle&#8221;). This may be misused in case the credentials are available with other person.<\/li>\n<li>Single sign-on also makes the authentication systems highly critical; a loss of their availability can result in denial of access to all systems unified under SSO.<\/li>\n<\/ol>\n<h3><span id=\"Criticisms\" class=\"mw-headline\">Supported Identity providers<\/span><\/h3>\n<p>Ephesoft Transact has been tested with the following SSO-related components (refer to the Overview at the start of this document for additional information):<\/p>\n<ul>\n<li><strong>SAML 2.0\u00a0<\/strong>\u2014 with the following identify providers:\n<ul>\n<li><strong>Okta<\/strong><\/li>\n<li><strong>PingFederate<\/strong><\/li>\n<li><strong>SSOCircle<\/strong><\/li>\n<\/ul>\n<\/li>\n<li><strong>CAS-based SSO Framework<\/strong><\/li>\n<\/ul>\n<p>If you would like to deploy SSO with another identity provider, please feel free to contact Support by emailing us at tickets@ephesoft.com<\/p>\n<h3><span id=\"Designs\" class=\"mw-headline\">Designs<\/span><\/h3>\n<p>Follow are the basic design patterns used to implement single sign on solutions.<\/p>\n<h3><span id=\"1._.C2.A0Ad-hoc_Encrypted_Token\" class=\"mw-headline\">1. \u00a0Ad-hoc Encrypted Token \u2014 Not currently supported<\/span><\/h3>\n<p>Applications use symmetric and public key cryptography to encrypt the application data that are used for SSO.\u00a0Refer to the following illustration:<\/p>\n<p><a href=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10001.jpg\"><img decoding=\"async\" class=\"alignnone wp-image-1292\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10001.jpg\" alt=\"400px-3.1_SingleSignOn_10001\" width=\"500\" height=\"303\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10001.jpg 400w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10001-300x181.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" \/><\/a><\/p>\n<p>This SSO design can be integrated with Ephesoft using Active Directory only. A key store has to be maintained in all the applications which are to be unified under SSO. Thus such a provision must be available on applications which are to be unified under SSO.<\/p>\n<p><b>Pros:<\/b><\/p>\n<ol>\n<li>This is easy to set up and implement.<\/li>\n<li>There is no dependency on another system.<\/li>\n<\/ol>\n<p><b>Cons:<\/b><\/p>\n<ol>\n<li>This is not a unified solution.<\/li>\n<li>Each site has to manage the cryptographic key.<\/li>\n<\/ol>\n<h3><span id=\"2._Using_third_party_SSO_agents_or_Identity_Management_Systems_like_OAM.2C_SiteMinder_etc.\" class=\"mw-headline\">2. Using Third-party SSO Agents or Identity Management Systems (IdPs) \u2014 Supported Method<\/span><\/h3>\n<p><span id=\"2._Using_third_party_SSO_agents_or_Identity_Management_Systems_like_OAM.2C_SiteMinder_etc.\" class=\"mw-headline\">This approach supports identity providers (IdPs) such as OAM, SiteMinder, and so on.\u00a0<\/span><\/p>\n<p>In this approach, the Ephesoft application uses the service provided by SSO agents. Refer to the following illustration.<\/p>\n<p><a href=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10002.jpg\"><img decoding=\"async\" class=\"alignnone wp-image-1293\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10002.jpg\" alt=\"400px-3.1_SingleSignOn_10002\" width=\"500\" height=\"319\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10002.jpg 400w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10002-300x191.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" \/><\/a><\/p>\n<p><b>The Ephesoft solution is currently based on this design (design # 2).<\/b><\/p>\n<h3><span id=\"Description\" class=\"mw-headline\">Description<\/span><\/h3>\n<p>Ephesoft application can now be configured using following security types:<\/p>\n<ol>\n<li>Ephesoft default Security using LDAP, AD, Tomcat.<\/li>\n<li>SSO authentication and Authorization at Ephesoft end using LDAP, AD etc.<\/li>\n<li>SSO authentication and authorization.<\/li>\n<\/ol>\n<p>The security type for the Ephesoft application can be configured in the <i>web.xml <\/i>file.<\/p>\n<p>The following properties must be configured in the web.xml file:<\/p>\n<p>1.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <b>authenticationType<\/b>\u00a0\u2014 context parameter for defining the security type mentioned above.<\/p>\n<p style=\"padding-left: 30px\">This property can be configured with the following values:<\/p>\n<ul>\n<li><b>0<\/b>\u00a0\u2014 Ephesoft default Security using LDAP, AD, and Tomcat<\/li>\n<li><b>1<\/b>\u00a0\u2014 SSO authentication and Authorization at Ephesoft end using LDAP, AD, and so on<\/li>\n<li><b>2<\/b>\u00a0\u2014 SSO authentication and authorization<\/li>\n<\/ul>\n<p style=\"padding-left: 30px\">Refer to the following illustration:<\/p>\n<p style=\"padding-left: 30px\"><a href=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Choose-authentication-type-1.png\"><img decoding=\"async\" class=\"alignnone wp-image-30628 size-large\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Choose-authentication-type-1-1024x101.png\" alt=\"\" width=\"840\" height=\"83\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Choose-authentication-type-1-1024x101.png 1024w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Choose-authentication-type-1-300x30.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Choose-authentication-type-1-768x76.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Choose-authentication-type-1.png 1293w\" sizes=\"(max-width: 840px) 100vw, 840px\" \/><\/a><\/p>\n<p>2.\u00a0 \u00a0 \u00a0 \u00a0When configuring the <b>authenticationType<\/b>\u00a0parameter cited above with a value of\u00a0 <b>1<\/b>\u00a0or <b>2<\/b>, then following parameters also must be configured:<\/p>\n<p style=\"padding-left: 30px\">A.\u00a0 \u00a0 \u00a0 The following parameters needs to be configured for the <b>authenticationFilter<\/b>\u00a0filter:<\/p>\n<ul>\n<li><b>requestUsernameHeader<\/b>\u00a0\u2014 This is used for defining the header name used by the SSO agent to set the user-name of authenticated user in the request. The same header name will be used by the Ephesoft application to fetch the desired information from the SSO agent. (This must be used for both types of security types, that is, 1 and 2.)<\/li>\n<li><b>logoutUrl<\/b>\u00a0\u2014 This is used for defining the logout URL where user will be redirected by the Ephesoft application after the user logs out by clicking on <strong>Sign-out<\/strong> button in the application. The complete URL is expected for this parameter value. (This must be used for both types of security types, that is, 1 and 2.)<\/li>\n<li><b>requestGroupnameHeader<\/b>\u00a0\u2014 This is used for defining the header name used by the SSO agent to set the group name which belongs to the authenticated user in the request. The same header name will be used by the Ephesoft application to fetch the desired information from SSO. Only one group name is expected for this header value. (This must be used only for security type 2.)<\/li>\n<li><b>requestSuperAdminHeader <\/b>\u2014This is used for defining the header name used by the SSO agent to set whether the group name belonged to the super admin role or not in the request. The same header name will be used by the Ephesoft application to fetch the desired information from the SSO agent. The values supported for this header are <strong>true<\/strong> and <strong>false<\/strong>. (This must be used only for security type 2.)<\/li>\n<\/ul>\n<p style=\"padding-left: 30px\">Refer to the following illustration for examples of these parameters:<\/p>\n<p style=\"padding-left: 30px\"><a href=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10004.jpg\"><img decoding=\"async\" class=\"size-full wp-image-1296 alignnone\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10004.jpg\" alt=\"400px-3.1_SingleSignOn_10004\" width=\"400\" height=\"265\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10004.jpg 400w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10004-300x198.jpg 300w\" sizes=\"(max-width: 400px) 100vw, 400px\" \/><\/a><\/p>\n<p style=\"padding-left: 30px\">B.\u00a0\u00a0\u00a0\u00a0\u00a0 All the <b>&lt;security-constraint&gt;<\/b>\u00a0and <b>&lt;login-config&gt; <\/b>settings must\u00a0be <b>commented<\/b> or <b>deleted <\/b>because these components are managed by the SSO agent.<\/p>\n<p style=\"padding-left: 30px\">C.\u00a0\u00a0\u00a0\u00a0\u00a0 A <b>default_group<\/b>\u00a0property has been added in the <b>application.properties<\/b>\u00a0file. This setting defines a default group to be used in case the group name is not provided in the request header.\u00a0(This must be used only for security type 2.)<\/p>\n<p style=\"padding-left: 30px\"><b>IMPORTANT: <\/b>For security types <strong>1<\/strong> and <strong>2<\/strong>, any realm configured for the Ephesoft application (configured for earlier shared releases) needs to be removed.<\/p>\n<h2>Defining Session Timeout Settings<\/h2>\n<p>Ephesoft Transact must be configured with the following settings, along with other configurations communicated from Ephesoft:<\/p>\n<p><b>Remove the new session timeout feature in cases where the authentication type is set to 1 or 2.<br \/>\nPerform the following steps:<\/b><\/p>\n<p>1. Comment the <strong><i>SessionTimeoutFilter<\/i>\u00a0<\/strong>and <strong><i>SessionTimoutServlet<\/i>\u00a0<\/strong>entries in\u00a0 the\u00a0<i>web.xml file.<\/i><\/p>\n<p style=\"padding-left: 30px\">Refer to the following illustration as a sample of these settings:<\/p>\n<p style=\"padding-left: 30px\"><a href=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Session-Timeout-Filter.png\"><img decoding=\"async\" class=\"alignnone wp-image-30631 size-large\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Session-Timeout-Filter-1024x508.png\" alt=\"\" width=\"840\" height=\"417\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Session-Timeout-Filter-1024x508.png 1024w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Session-Timeout-Filter-300x149.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Session-Timeout-Filter-768x381.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/Session-Timeout-Filter.png 1070w\" sizes=\"(max-width: 840px) 100vw, 840px\" \/><\/a><\/p>\n<p>2. Remove the entry of <i><strong>session-timeout.js<\/strong><\/i>\u00a0from all the <i>html<\/i> files.<\/p>\n<p style=\"padding-left: 30px\">Refer to the following illustration as a sample of this setting:<\/p>\n<p style=\"padding-left: 30px\"><a href=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/css-stylesheet.png\"><img decoding=\"async\" class=\"alignnone wp-image-30629 size-large\" src=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/css-stylesheet-1024x163.png\" alt=\"\" width=\"840\" height=\"134\" srcset=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/css-stylesheet-1024x163.png 1024w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/css-stylesheet-300x48.png 300w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/css-stylesheet-768x123.png 768w, https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2019\/02\/css-stylesheet.png 1209w\" sizes=\"(max-width: 840px) 100vw, 840px\" \/><\/a><\/p>\n<h3><span id=\"Conclusion_3\" class=\"mw-headline\">Conclusion<\/span><\/h3>\n<p>Ephesoft can now be integrated with single sign on (SSO) systems for purpose of authentication, authorization or both.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"featured_media":0,"parent":47681,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v19.0 (Yoast SEO v22.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Single Sign On | Ephesoft Docs<\/title>\n<meta name=\"robots\" content=\"noindex, follow\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Single Sign On\" \/>\n<meta property=\"og:description\" content=\"Overview Single sign-on\u00a0(SSO) is a mechanism of\u00a0access control\u00a0that can be applied on multiple related, but independent\u00a0software\u00a0systems. With this mechanism a [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/\" \/>\n<meta property=\"og:site_name\" content=\"Ephesoft Docs\" \/>\n<meta property=\"article:modified_time\" content=\"2020-12-03T21:48:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10001.jpg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/\",\"url\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/\",\"name\":\"Single Sign On | Ephesoft Docs\",\"isPartOf\":{\"@id\":\"https:\/\/ephesoft.com\/docs\/#website\"},\"datePublished\":\"2014-09-05T16:08:38+00:00\",\"dateModified\":\"2020-12-03T21:48:25+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/ephesoft.com\/docs\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Transact\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"System Configuration\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"User Connectivity\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Single Sign-On Resources\",\"item\":\"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/\"},{\"@type\":\"ListItem\",\"position\":6,\"name\":\"Single Sign On\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/ephesoft.com\/docs\/#website\",\"url\":\"https:\/\/ephesoft.com\/docs\/\",\"name\":\"Ephesoft Docs\",\"description\":\"Intelligent Document Processing Made Easy\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/ephesoft.com\/docs\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Single Sign On | Ephesoft Docs","robots":{"index":"noindex","follow":"follow"},"og_locale":"en_US","og_type":"article","og_title":"Single Sign On","og_description":"Overview Single sign-on\u00a0(SSO) is a mechanism of\u00a0access control\u00a0that can be applied on multiple related, but independent\u00a0software\u00a0systems. With this mechanism a [&hellip;]","og_url":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/","og_site_name":"Ephesoft Docs","article_modified_time":"2020-12-03T21:48:25+00:00","og_image":[{"url":"https:\/\/ephesoft.com\/docs\/wp-content\/uploads\/2014\/09\/400px-3.1_SingleSignOn_10001.jpg"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/","url":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/","name":"Single Sign On | Ephesoft Docs","isPartOf":{"@id":"https:\/\/ephesoft.com\/docs\/#website"},"datePublished":"2014-09-05T16:08:38+00:00","dateModified":"2020-12-03T21:48:25+00:00","breadcrumb":{"@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/single-sign-on\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/ephesoft.com\/docs\/"},{"@type":"ListItem","position":2,"name":"Transact","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/"},{"@type":"ListItem","position":3,"name":"System Configuration","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/"},{"@type":"ListItem","position":4,"name":"User Connectivity","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/"},{"@type":"ListItem","position":5,"name":"Single Sign-On Resources","item":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/"},{"@type":"ListItem","position":6,"name":"Single Sign On"}]},{"@type":"WebSite","@id":"https:\/\/ephesoft.com\/docs\/#website","url":"https:\/\/ephesoft.com\/docs\/","name":"Ephesoft Docs","description":"Intelligent Document Processing Made Easy","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/ephesoft.com\/docs\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"}]}},"comment_count":0,"_links":{"self":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/1291"}],"collection":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/comments?post=1291"}],"version-history":[{"count":0,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/1291\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/47681"}],"prev":[{"title":"SSO | CAS-Based SSO Framework","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/configurations\/user-connectivity\/single-sign-on-resources\/sso-cas-based-sso-framework\/","href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/docs\/15018"}],"wp:attachment":[{"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/media?parent=1291"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/ephesoft.com\/docs\/wp-json\/wp\/v2\/doc_tag?post=1291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}