SecURL FAQs
It is recommended that all links to the site go to the sign-in page.
The sign-in page in SecURL was designed to redirect to a specific landing page that you choose. This landing page is defined as the success URL in the sign-in page. All successful authentications will always redirect to the same success URL. Learn more
Yes. On the registration form you can set newly registered users to be automatically signed in using xmp-signin-auto="true". Learn more
Every PURL, even without SecURL, has the protection of an RID. SecURL adds another protection factor, which is the password. If you wish, you can add an additional factor by enabling User Name.
The "Forgot Password" functionality hasn't yet been implemented.
When you try to open a PURL and are then redirected to the sign-in page, you will see the PURL for a brief moment before being redirected. In certain pages you may even see an error message before the redirection.
It is recommended that all links to the site go to the sign-in page.
This can happen when you work with multiple recipients in the same browser. To avoid it, add the tag for clearing browser cookies when loading the sign-in page. Learn more
No. The whole point of security is not to reveal any personal information until after authentication.
When opening a PDF-on-Demand from an email, you are redirected to the document without passing through the secured site. The PDF-on-Demand is therefore not protected by SecURL. It is recommended to provide a link to a secure page, which contains a download link to the PDF-on-Demand.
This is the expected behavior of SecURL. It protects the ADOR which is flagged as the SecURL password and does not allow passing it.
This can sometimes happen when you work with both custom and managed websites, even when each is defined in a different project.
This can be solved by running the following command in the XMPL server: iisreset
For further details, contact the XMPie Support team.
New!! Take a look at XMPL V5 Beta