Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Support for RelayState to NPrinting SAML authentication and other limitations

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Frank_S
Support
Support

Support for RelayState to NPrinting SAML authentication and other limitations

Last Update:

Sep 9, 2021 4:53:40 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jul 30, 2019 12:48:24 PM

Is there a way to configure NPrinting NewsStand to land on different tabs based on the URLs after OKTA SSO?
  • Currently, we are using NPrinting NewsStand with OKTA Single Sign On (using SAML). The Qlik NPrinting NewsStand has two tabs: “Reports” and “Subscriptions”. We have a requirement: when user login to NPrinting NewsStand via OKTA Signgle Sign On, we want the user to land on the “Reports” tab, or “Subscriptions” tab based on the URL.
  • For example, if the OKTA Single Sign On URL is
[https://%3cokta-tenant%3e.oktapreview.com/app/%3cokta-app-id%3e/sso/saml?RelayState=/#/subscriptions]https://<okta-tenant>.oktapreview.com/app/<okta-app-id>/sso/saml?RelayState=/#/subscriptions
(Note the RelayState parameter), then the user should open the “Subscription” tab once they log in.
  • If the OKTA Single Sign On URL is
[https://%3cokta-tenant%3e.oktapreview.com/app/%3cokta-app-id%3e/sso/saml?RelayState=/#/repotrts]https://<okta-tenant>.oktapreview.com/app/<okta-app-id>/sso/saml?RelayState=/#/repotrts 

(Note that the RelayState parameter), then the user should open the “Reports” tab once they log in.
  • The above uses the “RelayState” parameter as an example, since “RelayState” is designed to do this type of job in SAML. However, the issue with “RelayState” state is, the redirect URL is a hashbang URL (the url /#/subscriptions has the hash sign # in it), which will be ignored by the browser during the redirect. The browser will redirect to the URL “/” and drop the rest of hashbang (the “#subscription” part).

 

! Qlik has previously received feedback on this feature and recorded the request for future review.  For up to date information and to express you would like the Feature implemented please write your specific requirement/feature request here:  Ideas | Qlik Community 
 

  • At the moment Qlik NPrinting doesn’t support the RelayState so it is not possible to implement the request at this time.
  • An internal feature request has been entered. ID is 2874
  • Any new update regarding feature request updates will appear in this article (if any). 
  • Feature update needs to be reviewed and approved by R&D before it is considered as a permanent future feature.

Feature Request ID(s):

  • 2784 - Add the support for RelayState to NPrinting SAML authentication
  • OP-7141 - Signing authentication requests and support encrypted responses

 

Other SAML limitations:

  • Qlik NPrinting does not sign the SAML authentication request. This means that identity providers that require the SAML authentication request to be signed are not supported.
  • SAML response encryption is not supported, so encrypted messages or attributes are not read by Qlik NPrinting.
  • SAML single logout is not supported

 

Related Information:

Labels (1)
Version history
Last update:
‎2021-09-09 04:53 AM
Updated by: