Common QPR Authentication - Revision history

Ollvihe at 13:13, 4 June 2024

2024-06-04T13:13:34Z

Ollvihe at 13:13, 4 June 2024

2024-06-04T13:13:13Z

Ollvihe: /* Configuring Common Authentication for QPR ProcessAnalyzer */

2024-06-04T13:12:48Z

Configuring Common Authentication for QPR ProcessAnalyzer

Ollvihe: /* Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service */

2019-06-28T14:48:12Z

Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service

Ollvihe: /* Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service */

2019-06-28T08:37:48Z

Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service

Ollvihe at 06:53, 3 June 2019

2019-06-03T06:53:14Z

Ollvihe: /* Configuring Common Authentication for QPR ProcessAnalyzer */

2019-06-03T06:52:39Z

Configuring Common Authentication for QPR ProcessAnalyzer

Ollvihe: /* Configuring Common Authentication for QPR ProcessAnalyzer */

2019-06-03T06:52:02Z

Configuring Common Authentication for QPR ProcessAnalyzer

Ollvihe: /* Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service */

2019-06-03T06:50:29Z

Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service

Ollvihe at 06:48, 3 June 2019

2019-06-03T06:48:56Z

@@ Line 1: / Line 1: @@
 Common authentication enables linking from one QPR product to the other without the need of a separate login for the product that is the link target. When you are authenticated to one QPR product, you are automatically authenticated all other QPR products as well. It is possible to configure a common authentication between following QPR products:
 * QPR Suite Portal
 * QPR Suite Web Services
 Common authentication works in a way that if there is a valid (non expired) session existing in any of the systems, sessions for the other systems are refreshed automatically without the need to login again. If all sessions have expired, there is a need to relogin. If a session has been expired, a valid session in other system is able to renew the expired session without notifying user.

@@ Line 10: / Line 10: @@
 In common authentication, '''username''' attribute is used to match user accounts between QPR products.
 == Configuring Common Authentication for QPR UI ==
@@ Line 18: / Line 26: @@
 # If the step 4 query didn't return anything, run the following:<br />'''INSERT INTO [DATABASENAME].[dbo].[CONFIGURATIONENTITY](KEY_FIELD,VALUE_FIELD) VALUES ('AUTHENTICATION_SERVICES', 'SETTINGSTRING');'''<br />(replace the SETTINGSTRING with the one determined in step 1).
 # If the step 4 query returned a row, run the following:<br />'''UPDATE [DATABASENAME].[dbo].[CONFIGURATIONENTITY] SET VALUE_FIELD = 'SETTINGSTRING' WHERE KEY_FIELD = 'AUTHENTICATION_SERVICES';'''<br />(replace the SETTINGSTRING with the one determined in step 1).
 == Embed QPR Suite Portal in QPR UI ==

← Older revision		Revision as of 13:12, 4 June 2024
Line 10:		Line 10:

	In common authentication, '''username''' attribute is used to match user accounts between QPR products.		In common authentication, '''username''' attribute is used to match user accounts between QPR products.
−
−	~~== Configuring Common Authentication for QPR ProcessAnalyzer ==~~
−	For QPR ProcessAnalyzer the common authentication is configured to the [[Web.config_file_in_QPR_ProcessAnalyzer\|'''web.config''']] file. Search the '''<Qpr.ProcessAnalyzer.Common.Properties.Settings>''' section in the file containing placeholders for the settings '''ServerGroupPA''', '''ServerGroupMD''' and '''ServerGroupMEA'''. To create a common authentication group to QPR UI, define the QPR UI url to the ServerGroupMD setting. To create a common authentication group to QPR Suite, define the QPR Suite url to the ServerGroupMEA setting. The setting ServerGroupPA is for creating an authentication group to another QPR ProcessAnalyzer server.
−
−	~~In the following example, the '''SERVERNAME''' needs to be replaced with the name of the corresponding QPR server:~~
−	~~<pre>~~
−	~~<setting name="ServerGroupMD" serializeAs="Xml">~~
−	~~<value>~~
−	~~<ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">~~
−	~~<string>http://SERVERNAME:8080/EnticeServices/</string>~~
−	~~</ArrayOfString>~~
−	~~</value>~~
−	~~</setting>~~
−	~~<setting name="ServerGroupMEA" serializeAs="Xml">~~
−	~~<value>~~
−	~~<ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">~~
−	~~<string>http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</string>~~
−	~~</ArrayOfString>~~
−	~~</value>~~
−	~~</setting>~~
−	~~</pre>~~

	== Configuring Common Authentication for QPR UI ==		== Configuring Common Authentication for QPR UI ==

@@ Line 47: / Line 47: @@
 # If using QPR Suite 2019.1 or later, add the following line to the '''[WAS Settings]''' section:<br>'''<nowiki>AuthenticationService_1=WAS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</nowiki>'''<br>It's important that the servername and protocol are same as defined in the '''HostScriptLocation''' setting (in the [WAS Settings] section). Also, increase the number in the setting name if AuthenticationService_1 and/or AuthenticationService_2 are already used. This setting is needed for the QPR Suite Web Service (WS) to use the common authentication to validate a session token from QPR Suite Web Application server (WAS).
 # Restart QPR Suite Windows service.
 == Embed QPR Suite Portal in QPR UI ==

@@ Line 45: / Line 45: @@
 # If you are adding the common authentication to QPR UI, in the '''[WAS Settings]''' section, add <br> '''<nowiki>AuthenticationService_1=ENTICE,http://SERVERNAME:8080</nowiki>''' <br> SERVERNAME is the name of the QPR UI server that is used when accessing QPR UI (note that the url does not contain a path part, such as ''EnticeServices''). If you also need to add common authentication to QPR ProcessAnalyzer, add<br>'''<nowiki>AuthenticationService_2=PA,http://SERVERNAME</nowiki>'''<br>as a new line. Also, increase the number in the setting name if AuthenticationService_1 is already used.
 # If using QPR Suite 2019.1 or later, check also that in the '''[WAS Settings]''' section, '''UseAuthenticationToken''' is set to '''1'''.
-# If using QPR Suite 2019.1 or later, add the following line to the '''[WAS Settings]''' section:<br>'''<nowiki>AuthenticationService_1=WAS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</nowiki>'''<br>It's important that the servername and protocol are same as defined in the '''HostScriptLocation''' setting (in the [WAS Settings] section). Also, increase the number in the setting name if AuthenticationService_1 and/or AuthenticationService_2 are already used. This setting is needed for the QPR Suite Web Service to use the common authentication to validate a session token from QPR Suite Web Application server (WAS).
+# If using QPR Suite 2019.1 or later, add the following line to the '''[WAS Settings]''' section:<br>'''<nowiki>AuthenticationService_1=WAS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</nowiki>'''<br>It's important that the servername and protocol are same as defined in the '''HostScriptLocation''' setting (in the [WAS Settings] section). Also, increase the number in the setting name if AuthenticationService_1 and/or AuthenticationService_2 are already used. This setting is needed for the QPR Suite Web Service (WS) to use the common authentication to validate a session token from QPR Suite Web Application server (WAS).
 # Restart QPR Suite Windows service.

@@ Line 10: / Line 10: @@
 In common authentication, '''username''' attribute is used to match user accounts between QPR products.
 == Configuring Common Authentication for QPR ProcessAnalyzer ==
@@ Line 39: / Line 31: @@
 </setting>
 </pre>
 == Configuring Common Authentication for QPR Suite Portal and QPR Suite Web Service ==

@@ Line 35: / Line 35: @@
      <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
        <string>http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</string>
      </ArrayOfString>
    </value>

@@ Line 50: / Line 50: @@
 # In the QPR application server, open file '''C:\ProgramData\QPR Software\QPR 2019\2019.1\Servers\Settings\QPR_Servers.ini'''. Note that you may have other version than QPR Suite 2019.
 # In the '''[UMS Settings]''' section, set '''EnableSSOForPortal=1''' (if EnableSSOForPortal setting already exists, change the existing setting. If the setting doesn't exist, create it as a new).
-# If you are adding the common authentication to QPR UI, in the '''[WAS Settings]''' section, add <br> '''<nowiki>AuthenticationService_1=ENTICE,http://SERVERNAME:8080</nowiki>''' <br> SERVERNAME is the name of the QPR UI server that is used when accessing QPR UI (note that the url does not contain a path part, such as ''EnticeServices''). If you also need to add common authentication to QPR ProcessAnalyzer, add<br>'''<nowiki>AuthenticationService_2=PA,http://SERVERNAME</nowiki>'''<br>as a new line. Note the increasing number in the setting name if AuthenticationService_1 is already used.
+# If you are adding the common authentication to QPR UI, in the '''[WAS Settings]''' section, add <br> '''<nowiki>AuthenticationService_1=ENTICE,http://SERVERNAME:8080</nowiki>''' <br> SERVERNAME is the name of the QPR UI server that is used when accessing QPR UI (note that the url does not contain a path part, such as ''EnticeServices''). If you also need to add common authentication to QPR ProcessAnalyzer, add<br>'''<nowiki>AuthenticationService_2=PA,http://SERVERNAME</nowiki>'''<br>as a new line. Also, increase the number in the setting name if AuthenticationService_1 is already used.
 # If using QPR Suite 2019.1 or later, check also that in the '''[WAS Settings]''' section, '''UseAuthenticationToken''' is set to '''1'''.
-# If using QPR Suite 2019.1 or later, add the following line to the '''[WAS Settings]''' section:<br>'''<nowiki>AuthenticationService_1=WAS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</nowiki>'''<br>It's important that the servername and protocol are same as defined in the '''HostScriptLocation''' setting (in the [WAS Settings] section). Note also the increasing number in the setting name if AuthenticationService_1 and/or AuthenticationService_2 are already used. This setting is needed for the QPR Suite Web Service to use the common authentication to validate a session token from QPR Suite Web Application server (WAS).
+# If using QPR Suite 2019.1 or later, add the following line to the '''[WAS Settings]''' section:<br>'''<nowiki>AuthenticationService_1=WAS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</nowiki>'''<br>It's important that the servername and protocol are same as defined in the '''HostScriptLocation''' setting (in the [WAS Settings] section). Also, increase the number in the setting name if AuthenticationService_1 and/or AuthenticationService_2 are already used. This setting is needed for the QPR Suite Web Service to use the common authentication to validate a session token from QPR Suite Web Application server (WAS).
 # Restart QPR Suite Windows service.

@@ Line 13: / Line 13: @@
 == Configuring Common Authentication for QPR UI ==
 To configure Common Authentication for QPR UI, follow these instructions:
-# Determine the needed setting string as follows: it uses format PRODUCTNAME,URL;PRODUCTNAME,URL;... where PRODUCTNAME is either '''WAS''', '''WS''' or '''PA'''. Example:<pre><nowiki>PA,http://localhost/QPRPA/MainService.svc/webHttp/;WAS,http://SERVERNAME/QPR/Portal/QPR.Isapi.dll;WS,http://SERVERNAME/QPR/Portal/QPR.Isapi.dll/wsforward/MainService.svc/webHttp/;</nowiki></pre> SERVERNAME is the name of the corresponding server.
+# Determine the needed setting string as follows: it uses format PRODUCTNAME,URL;PRODUCTNAME,URL;... where PRODUCTNAME is either '''WAS''', '''WS''' or '''PA'''. Example:<pre><nowiki>PA,http://localhost/QPRPA/MainService.svc/webHttp/;WAS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll;WS,http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll/wsforward/MainService.svc/webHttp/;</nowiki></pre> SERVERNAME is the name of the corresponding server.
 # Login to the QPR UI database using '''SQL Server Management Studio'''.
 # Right click QPR UI database, select '''New Query''', and define following query:<br />'''SELECT VALUE_FIELD FROM [DATABASENAME].[dbo].[CONFIGURATIONENTITY] WHERE KEY_FIELD ='AUTHENTICATION_SERVICES';'''<br />If the query returns a row, store the result for backup.
@@ Line 41: / Line 41: @@
    <value>
      <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
-       <string>http://SERVERNAME/QPR/Portal/QPR.Isapi.dll</string>
+       <string>http://SERVERNAME/QPR2019-1/Portal/QPR.Isapi.dll</string>
      </ArrayOfString>
    </value>