Swivel Knowledgebase Wiki - Recent changes [en]

Microsoft OWA 2010 IIS Integration

2012-05-17T10:03:28Z

Prerequisites:

← Older revision		Revision as of 10:03, 17 May 2012
Line 55:		Line 55:
	[http://kb.swivelsecure.com/wiki/images/a/a5/IISFilterOWA2010SP1.zip IIS Filter for OWA 2010 with service pack 1]		[http://kb.swivelsecure.com/wiki/images/a/a5/IISFilterOWA2010SP1.zip IIS Filter for OWA 2010 with service pack 1]

-	[http://kb.swivelsecure.com/wiki/images/6/64/~~IISFilterOWA2010Beta~~.zip Beta release for SP1 with support for multiple PINsafe servers]	+	[http://kb.swivelsecure.com/wiki/images/a/a2/IISFilterOWA2010.2.4.zip Beta release for SP1 with support for multiple PINsafe servers]
-		+

	==Architecture==		==Architecture==

PINsafe Evaluation

2012-05-17T09:34:00Z

PINsafe Evaluation:

← Older revision		Revision as of 09:34, 17 May 2012
Line 4:		Line 4:


-	Software download (available ~~on website)~~	+	Software download, available here [[PINsafe software]]

	VMWare Image see [[VMWare How To Guide]]		VMWare Image see [[VMWare How To Guide]]

Appliance Disk full

2012-05-16T13:44:57Z

← Older revision		Revision as of 13:44, 16 May 2012
Line 28:		Line 28:
	== /var/lib/mysql ==		== /var/lib/mysql ==

-	Transaction logs may build up in /var/lib/mysql, this is caused by A/A appliances being out of synchronisation.	+	Transaction logs may build up in /var/lib/mysql, this is caused by A/A appliances being out of synchronisation. The transaction logs consist of binaries that contain data edits and/or relays that is information sent to a MySQL slave.

Locating memberOf Groups How To Guide

2012-05-16T13:15:08Z

← Older revision		Revision as of 13:15, 16 May 2012
(11 intermediate revisions not shown)
Line 12:		Line 12:
	It can become difficult to quickly tell which of the groups a user is a member of is responsible for the user still being synced into PINsafe.		It can become difficult to quickly tell which of the groups a user is a member of is responsible for the user still being synced into PINsafe.

-	This article demonstrates an easy way to find which groups are members of the defined PINsafe group.	+	This article demonstrates an easy way to find which groups are members of the defined PINsafe group, so that you may compare those groups with the groups you know a member still belongs to.


Line 31:		Line 31:
	==Solution==		==Solution==

-	* Using Softerra, define a new connection to the LDAP or Active Directory server;	+	* Using Softerra LDAP Browser, define a new profile/connection to the LDAP or Active Directory server;
-	* As you expand the directory structure, Softerra will begin to retrieve and cache information about the directory;	+	* As you expand the directory structure, Softerra will begin to retrieve and cache information about the directory. It may take some time;
	* Click the top-most entry in the directory;		* Click the top-most entry in the directory;
	* Click the Directory Search button (or press Ctrl+F);		* Click the Directory Search button (or press Ctrl+F);
		+
		+
		+	[[Image:ObjectClassGroup.png]]
		+
		+
	* In the 'Search DN' field enter the base DN, e.g. '''DC=swivel, DC=local'''		* In the 'Search DN' field enter the base DN, e.g. '''DC=swivel, DC=local'''
-	* In the 'Filter' field enter this filter, using the PINsafe Group that you know the user was removed from, e.g. '''(&(objectClass=group)(memberOf=~~(&(objectClass=group)(memberOf~~=CN=PINsafeUsers,OU=~~PINsafe Membership~~,DC=Swivel,DC=Local))''' where in this example the group the user was removed from	+	* In the 'Filter' field enter this filter, using the PINsafe Group that you know the user was removed from, e.g.
		+
		+	'''(&(objectClass=group)(memberOf=<span style="color:#FF0000">CN=PINsafeUsers,OU=Example,DC=Swivel,DC=Local</span>))'''
		+
		+	...where in this example the group the user was removed from is highlighted with a different colour;
		+
		+	* Click 'Search';
		+	* The Directory Search may take some time to retrieve the query from the LDAP server, but eventually it should return a list of groups that belong to that PINsafe group.
		+	* Analyse this list of groups to determine if your problematic user exists within them. If they do, then you can investigate whether:
		+	** The user can be removed from the group contained within those groups, or:
		+	** if the entire group contained within the PINsafe group should even be a member of the PINsafe group.

File:ObjectClassGroup.png

2012-05-16T12:50:44Z

uploaded "[[File:ObjectClassGroup.png]]"

New page

Locating memberOf Groups How To Guide

2012-05-16T12:48:21Z

New page

{{Template:default}}
{{Template:how}}

==Overview==

On large installations where other teams take care of directory management, it is often the case that other user groups are added to PINsafe groups which are used by PINsafe.

Despite removing a user from a Repository Group defined within PINsafe, the user still remains within PINsafe after a user sync. This is due to being referenced by a group which is a member of the defined group.

So whilst a user is no longer directly a member of the group defined for use by PINsafe, the user is still synced in because the user is a member of the group contained within the group referenced by PINsafe.

It can become difficult to quickly tell which of the groups a user is a member of is responsible for the user still being synced into PINsafe.

This article demonstrates an easy way to find which groups are members of the defined PINsafe group.

==Symptoms==

User still appears in PINsafe after a User Sync, despite having been removed from the group defined under Repository -> Groups.

==Prerequisites==

* We recommend the use of third-party software from Softerra called LDAP Browser. This is available as freeware and as a commercial paid-for product. Available here: http://www.ldapbrowser.com/

* You will need the credentials that PINsafe uses to bind to the particular repository that the user belongs to. These are already listed under the Repository definition within PINsafe, but you will need to know the password;

* You will require network access to the Repository server, e.g. Active Directory or LDAP, using the same network details defined on the Repository configuration screen within PINsafe.

==Solution==

* Using Softerra, define a new connection to the LDAP or Active Directory server;
* As you expand the directory structure, Softerra will begin to retrieve and cache information about the directory;
* Click the top-most entry in the directory;
* Click the Directory Search button (or press Ctrl+F);
* In the 'Search DN' field enter the base DN, e.g. '''DC=swivel, DC=local'''
* In the 'Filter' field enter this filter, using the PINsafe Group that you know the user was removed from, e.g. '''(&(objectClass=group)(memberOf=(&(objectClass=group)(memberOf=CN=PINsafeUsers,OU=PINsafe Membership,DC=Swivel,DC=Local))''' where in this example the group the user was removed from

Webmin How To Guide

2012-05-15T16:33:55Z

← Older revision		Revision as of 16:33, 15 May 2012
Line 114:		Line 114:
	* [[MON Service Monitor How to guide]]		* [[MON Service Monitor How to guide]]
	* [[How to run PINsafe on non-default ports]]		* [[How to run PINsafe on non-default ports]]
		+	* [[ResetPIN How To Guide]]
		+	* [[ChangePIN How to Guide]]

File:ADFS.zip

2012-05-15T15:46:33Z

uploaded a new version of "[[File:ADFS.zip]]" Fixed exists.aspx

New page

Appliance Disk full

2012-05-15T13:58:01Z

← Older revision		Revision as of 13:58, 15 May 2012
(One intermediate revision not shown)
Line 19:		Line 19:

	Where depth is the number of folders to look within		Where depth is the number of folders to look within
		+
		+
		+	== /var/log/messages ==
		+
		+	Log files may build up in /var/log/messages
		+
		+
		+	== /var/lib/mysql ==
		+
		+	Transaction logs may build up in /var/lib/mysql, this is caused by A/A appliances being out of synchronisation.
		+
		+
		+	== PINsafe 3.7.3727 ==
		+
		+	Pinsafe 3.7.3727 contains debugging information for Repository syncs that may produce a large number of files and the files may need to be purged. To prevent the files being generated upgrade to a more recent version of PINsafe. As a temporary measure they can be deleted and a low frequency of repository sync can be set. The files are named:
		+
		+	profile.<date>.data
		+
		+	and reside in:
		+
		+	<path to Tomcat>/webapps/pinsafe/WEB-INF/logs

Mobile Re-Provision How to Guide

2012-05-15T13:00:36Z

← Older revision		Revision as of 13:00, 15 May 2012
Line 25:		Line 25:
	== Connecting to Provision ==		== Connecting to Provision ==

-	Appliance: https://IP:8443/provision.jsp	+	Appliance: https://IP:8443/resetpin/provision.jsp

-	software install: http://IP:8080/provision.jsp	+	software install: http://IP:8080/resetpin/provision.jsp

File:CAGEE 8 files.zip

2012-05-14T15:41:56Z

uploaded a new version of "[[File:CAGEE 8 files.zip]]" Fixed angled quotation mark in js file.

New page

Juniper SA 7.x Integration

2012-05-10T17:07:11Z

← Older revision		Revision as of 17:07, 10 May 2012
Line 219:		Line 219:
	A new policy and role may be required for this. Select Resource Policies/Web Access Policies/<Policy Name>/General, under Resources enter the PINsafe internal address:		A new policy and role may be required for this. Select Resource Policies/Web Access Policies/<Policy Name>/General, under Resources enter the PINsafe internal address:

-	Example https://pinsafe.swivel.local:~~844~~/proxy/*	+	Example https://pinsafe.swivel.local:8443/proxy/*

	For Roles select Policy Applies to selected roles, add the required role to the selected roles.		For Roles select Policy Applies to selected roles, add the required role to the selected roles.

AGENT ERROR NO SECURITY STRINGS

2012-05-10T16:31:18Z

← Older revision		Revision as of 16:31, 10 May 2012
Line 21:		Line 21:

	'''Login failed for user:username, error: The user does not have any security strings suitable for the authentication.'''		'''Login failed for user:username, error: The user does not have any security strings suitable for the authentication.'''
		+
		+	Repeated authentication attempts may cause accounts to become locked.


Line 40:		Line 42:

	*PINsafe 3.8.4256 has an error whereby On demand authentication security strings do not match those in the View Security strings.		*PINsafe 3.8.4256 has an error whereby On demand authentication security strings do not match those in the View Security strings.
		+
		+	* The account has become locked

AGENT ERROR NO SECURITY STRINGS

2012-05-10T16:16:07Z

Solution:

← Older revision		Revision as of 16:16, 10 May 2012
Line 35:		Line 35:
	*The access device is adding the domain name to the authentication in the format domain\username		*The access device is adding the domain name to the authentication in the format domain\username

-	*A user is attempting a single channel authentication, but the single channel request has not reached PINsafe	+	*A user is attempting a single channel authentication, but their account is locked, disabled or deleted. They will get a dummy security string, but that is not valid for authentication.
		+
		+	*A user is attempting a single channel authentication, but the single channel request has not reached PINsafe.

	*PINsafe 3.8.4256 has an error whereby On demand authentication security strings do not match those in the View Security strings.		*PINsafe 3.8.4256 has an error whereby On demand authentication security strings do not match those in the View Security strings.

Error Messages

2012-05-10T16:11:05Z

← Older revision		Revision as of 16:11, 10 May 2012
Line 175:		Line 175:
	'''Login failed for user:username, error: The user does not have any security strings suitable for the authentication.'''		'''Login failed for user:username, error: The user does not have any security strings suitable for the authentication.'''

-	~~The user is attempting a dual channel authentication, but the user has not been sent any security strings. This can be because:~~	+	See [[AGENT_ERROR_NO_SECURITY_STRINGS]]
-		+
-	~~No transport has been defined for the security strings to be sent~~	+
-		+
-	~~Older versions of PINsafe did not send the security strings if users were added to a group~~	+
-		+
-	~~The access device is adding the domain name to the authentication in the format domain\username~~	+
-		+
-	~~A user is attempting a single channel authentication, but the single channel request has not reached PINsafe~~	+
-		+
-	~~PINsafe 3.8.4256 has an error whereby On demand authentication security strings do not match those in the View Security strings.~~	+

AGENT ERROR NO SECURITY STRINGS

2012-05-10T16:09:38Z

New page

[[Image:logo.gif]]

[[Category:symptom]]

==Overview==

The error ''AGENT ERROR NO SECURITY STRINGS'' can be seen in a number of different circumstances, this document covers how to troubleshoot the issues involved.

==Prerequisites==

PINsafe 3.x

==Symptoms==

'''RADIUS: <0> Access-Request(1) LEN=192.168.0.1:1001 Access Request by username Failed: AccessRejectException: AGENT_ERROR_NO_SECURITY_STRINGS'''

and

'''Login failed for user:username, error: The user does not have any security strings suitable for the authentication.'''

==Solution==

The user is attempting a dual channel authentication, but the user has not been sent any security strings. This can be because:

*A single channel security string is being requested from one PINsafe instance, but the authentications are being made against another PINsafe instance. Since the PINsafe instance carrying out an authentication has not received any single channel session starts it produces the AGENT_ERROR_NO_SECURITY_STRINGS message. Enable [[Session Sharing]] or [http://kb.swivelsecure.com/wiki/index.php/RADIUS_How_To_Guide#PINsafe_RADIUS_Proxy PINsafe RADIUS Proxy].

*No transport has been defined for the security strings to be sent

*Older versions of PINsafe did not send the security strings if users were added to a group

*The access device is adding the domain name to the authentication in the format domain\username

*A user is attempting a single channel authentication, but the single channel request has not reached PINsafe

*PINsafe 3.8.4256 has an error whereby On demand authentication security strings do not match those in the View Security strings.

Symptoms

2012-05-10T16:01:06Z

← Older revision		Revision as of 16:01, 10 May 2012
Line 19:		Line 19:

	[[Agent and NAS entries incorrectly displayed]]		[[Agent and NAS entries incorrectly displayed]]
		+
		+	[[AGENT_ERROR_NO_SECURITY_STRINGS]]

	[[Appliance Disk full]]		[[Appliance Disk full]]

Upgrading PINsafe on Microsoft Windows

2012-05-10T15:58:35Z

Upgrade PINsafe

2012-05-10T15:56:15Z

← Older revision		Revision as of 15:56, 10 May 2012
Line 236:		Line 236:
	cp –p /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf/ranges.xml /root/upgrade		cp –p /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf/ranges.xml /root/upgrade

-	4. Back up the PINsafe User Repository by taking a copy of .../WEB-INF/data/repository.xml to a safe location.	+	4. Back up the PINsafe ranges file by taking a copy of .../WEB-INF/conf/config.properties to a safe location.
		+	cp –p /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf/config.properties /root/upgrade
		+
		+	5. Back up the PINsafe User Repository by taking a copy of .../WEB-INF/data/repository.xml to a safe location.
	cp –p /usr/local/tomcat/webapps/pinsafe/WEB-INF/data/repository.xml /root/upgrade		cp –p /usr/local/tomcat/webapps/pinsafe/WEB-INF/data/repository.xml /root/upgrade

-	5. Back up the PINsafe user data by taking a copy of everything under .../WEB-INF/db to a safe location. This is only relevant if you are using the Internal database.	+	6. Back up the PINsafe user data by taking a copy of everything under .../WEB-INF/db to a safe location. This is only relevant if you are using the Internal database.
	cp –rp /usr/local/tomcat/webapps/pinsafe/WEB-INF/db /root/upgrade		cp –rp /usr/local/tomcat/webapps/pinsafe/WEB-INF/db /root/upgrade

-	6. If you have any custom transport classes, note that classes from 3.5 or earlier are not compatible with 3.6, 3.7 or 3.8. Check with Swivel Secure if there is an upgrade available. As a matter of principle, when Swivel Secure develops a custom transport class for a customer, it is included as a standard component in the next release of PINsafe. Please check with Swivel that your transport is available and/or still valid before upgrading.	+	7. If you have any custom transport classes, note that classes from 3.5 or earlier are not compatible with 3.6, 3.7 or 3.8. Check with Swivel Secure if there is an upgrade available. As a matter of principle, when Swivel Secure develops a custom transport class for a customer, it is included as a standard component in the next release of PINsafe. Please check with Swivel that your transport is available and/or still valid before upgrading.

-	7. Back up the PINsafe logs by taking a copy of everything under .../WEB-INF/logs to a safe location. The upgrade will not fail if you do not backup logs, but you will not be able to view old log entries.	+	8. Back up the PINsafe logs by taking a copy of everything under .../WEB-INF/logs to a safe location. The upgrade will not fail if you do not backup logs, but you will not be able to view old log entries.
	cp –rp /usr/local/tomcat/webapps/pinsafe/WEB-INF/logs /root/upgrade		cp –rp /usr/local/tomcat/webapps/pinsafe/WEB-INF/logs /root/upgrade

-	8. If the Internal, or MySQL DB is not being used, backup the DB driver file ../WEB-INF/lib (check with Swivel Secure the name of the driver file).	+	9. If the Internal, or MySQL DB is not being used, backup the DB driver file ../WEB-INF/lib (check with Swivel Secure the name of the driver file).
	cp -p /usr/local/tomcat/webapps/pinsafe/WEB-INF/lib/<driver>.jar /root/upgrade		cp -p /usr/local/tomcat/webapps/pinsafe/WEB-INF/lib/<driver>.jar /root/upgrade

-	9. Remove the current PINsafe installation by deleting the pinsafe.war file. Tomcat will remove the associated directory.	+	10. Remove the current PINsafe installation by deleting the pinsafe.war file. Tomcat will remove the associated directory.
	service tomcat5 start		service tomcat5 start
	rm –f /usr/local/tomcat/webapps/pinsafe.war		rm –f /usr/local/tomcat/webapps/pinsafe.war
	service tomcat5 restart		service tomcat5 restart

-	10. Copy new pinsafe.war file to the webapps folder.	+	11. Copy new pinsafe.war file to the webapps folder.
	cp –p /root/pinsafe.war /usr/local/tomcat/webapps		cp –p /root/pinsafe.war /usr/local/tomcat/webapps

-	11. Stop the Tomcat service.	+	12. Stop the Tomcat service.
	service tomcat5 stop		service tomcat5 stop

-	12. Restore the config.xml file to .../WEB-INF/conf/config.xml	+	13. Restore the config.xml file to .../WEB-INF/conf/config.xml

	cp –p /root/upgrade/config.xml /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf		cp –p /root/upgrade/config.xml /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf

-	13. Restore the ranges.xml file to .../WEB-INF/conf/ranges.xml	+	14. Restore the ranges.xml file to .../WEB-INF/conf/ranges.xml
	cp –p /root/upgrade/ranges.xml /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf		cp –p /root/upgrade/ranges.xml /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf

-	14. If an internal database is being used, restore the database.	+	15. Restore the config.properties file to .../WEB-INF/conf/config.properties
		+	cp –p /root/upgrade/config.properties /usr/local/tomcat/webapps/pinsafe/WEB-INF/conf
		+
		+	16. If an internal database is being used, restore the database.
	cp -rp /root/upgrade/db/* /usr/local/tomcat/webapps/pinsafe/WEB-INF/db/		cp -rp /root/upgrade/db/* /usr/local/tomcat/webapps/pinsafe/WEB-INF/db/

-	15. If an XML repository is being used restore the repository.xml file.	+	17. If an XML repository is being used restore the repository.xml file.
	cp –p /root/upgrade/repository.xml /usr/local/tomcat/webapps/pinsafe/WEB-INF/data		cp –p /root/upgrade/repository.xml /usr/local/tomcat/webapps/pinsafe/WEB-INF/data

-	16. Restore your custom transport classes if relevant.	+	18. Restore your custom transport classes if relevant.

-	17. Restore the old log files.	+	19. Restore the old log files.
	cp –rp /root/upgrade/logs/* /usr/local/tomcat/webapps/pinsafe/WEB-INF/logs		cp –rp /root/upgrade/logs/* /usr/local/tomcat/webapps/pinsafe/WEB-INF/logs

-	18. Restore the JDBC driver file if you backed it up (replace the name of the driver with the name used previously)	+	20. Restore the JDBC driver file if you backed it up (replace the name of the driver with the name used previously)
	cp -p /root/upgrade/<driver>.jar /usr/local/tomcat/webapps/pinsafe/WEB-INF/lib/		cp -p /root/upgrade/<driver>.jar /usr/local/tomcat/webapps/pinsafe/WEB-INF/lib/

-	19. Ensure that the ownerships and permissions on the files that have been restored are correct.	+	21. Ensure that the ownerships and permissions on the files that have been restored are correct.
	chown –R swivel:swivel /usr/local/tomcat/webapps/pinsafe		chown –R swivel:swivel /usr/local/tomcat/webapps/pinsafe
	chmod –R 775 /usr/local/tomcat/webapps/pinsafe/WEB-INF/db		chmod –R 775 /usr/local/tomcat/webapps/pinsafe/WEB-INF/db

-	20. Start the Tomcat service.	+	22. Start the Tomcat service.
	service tomcat5 start		service tomcat5 start

Line 360:		Line 366:
	service heartbeat start		service heartbeat start
	service mon start		service mon start
		+

	==Additional Information==		==Additional Information==

Appliance Disk full

2012-05-10T11:27:27Z

← Older revision		Revision as of 11:27, 10 May 2012
Line 56:		Line 56:
	== Manually deleting files ==		== Manually deleting files ==

-	Note: Take care when using the rm command so that only the correct files are deleted. Deleted files can only be recovered from valid backups.	+	'''Note: Take care when using the rm command so that only the correct files are deleted. Deleted files can only be recovered from valid backups.'''
		+
		+	The following commands are run from the command line, see [[Command Line Access How to guide]]

	* Ensure that you are in the correct directory		* Ensure that you are in the correct directory
Line 64:		Line 66:

	find . -iname 'localhost.*' \| xargs rm		find . -iname 'localhost.*' \| xargs rm
		+
		+
		+	=== Deleting log files ===
		+
		+	To delete log files older than 5 days the following commands can be used.
		+
		+	find /var/log/tomcat/ -iname 'localhost.*' -mtime +5 \| xargs rm
		+
		+
		+	find /var/log/tomcat/ -iname 'manager.*' -mtime +5 \| xargs rm
		+
		+
		+	find /var/log/tomcat/ -iname 'catalina.*' -mtime +5 \| xargs rm
		+
		+
		+	find /var/log/tomcat/ -iname 'admin.*' -mtime +5 \| xargs rm
		+
		+
		+	find /var/log/tomcat/ -iname 'host-manager.*' -mtime +5 \| xargs rm

Citrix Web Interface 5.X additional login page options

2012-05-10T10:55:41Z

← Older revision		Revision as of 10:55, 10 May 2012
Line 51:		Line 51:

	<nowiki>To make sure the new button looks right, you will also need to edit app_data/include/loginStyle.inc. Look for occurrences of #otcButtonWrapper and add ", #msgButtonWrapper". Also, for the entry #<%=Constants.ID_OTC_BTN%>, add ", #dcmessage".</nowiki>		<nowiki>To make sure the new button looks right, you will also need to edit app_data/include/loginStyle.inc. Look for occurrences of #otcButtonWrapper and add ", #msgButtonWrapper". Also, for the entry #<%=Constants.ID_OTC_BTN%>, add ", #dcmessage".</nowiki>
		+
		+
		+	To change the Refresh Image button modify the file under auth\clientscripts\login.js.add and search for the line Refresh Image and change to the required text, such as Request Code or Request SMS.
		+
		+	<nowiki> "<span class='rightDoor'>Refresh Image</span>" +"</nowiki>

File:PINsafeTMGFilter.1.3.3.zip

2012-05-10T10:53:03Z

uploaded a new version of "[[File:PINsafeTMGFilter.1.3.3.zip]]"

New page

File:PINsafeMSUAGsp1SingleChannellogin.zip

2012-05-10T10:47:31Z

uploaded a new version of "[[File:PINsafeMSUAGsp1SingleChannellogin.zip]]" This time the right file!

New page

File:PINsafeTMGFilter.1.3.3.zip

2012-05-10T09:54:46Z

uploaded a new version of "[[File:PINsafeTMGFilter.1.3.3.zip]]" Oops! Forgot to fix the original error!

New page

File:PINsafeTMGFilter.1.3.3.zip

2012-05-10T09:21:27Z

uploaded "[[File:PINsafeTMGFilter.1.3.3.zip]]" Adds a cookie that should help with single sign-on.

New page

File:PINsafeMSUAGsp1SingleChannellogin.zip

2012-05-10T09:14:32Z

uploaded a new version of "[[File:PINsafeMSUAGsp1SingleChannellogin.zip]]"

New page

← Older revision		Revision as of 15:58, 10 May 2012
Line 21:		Line 21:

	If an external database such as MySQL or MSSQL is used make a backup of the database, since it may be modified if it was upgraded and you may need to go back to the previous version database state should something go wrong.		If an external database such as MySQL or MSSQL is used make a backup of the database, since it may be modified if it was upgraded and you may need to go back to the previous version database state should something go wrong.
		+

	== Moving PINsafe to another server ==		== Moving PINsafe to another server ==
Line 33:		Line 34:

	See below specific information on each of these steps.		See below specific information on each of these steps.
		+

	== Upgrading PINsafe on the same server ==		== Upgrading PINsafe on the same server ==
Line 47:		Line 49:

	See below specific information on each of these steps.		See below specific information on each of these steps.
		+

	== Microsoft Windows PINsafe Upgrade steps ==		== Microsoft Windows PINsafe Upgrade steps ==
Line 55:		Line 58:

	If you upgrade Java, make sure that Tomcat is reconfigured to use the new version. The simplest way to do this is through the Tomcat Control Panel. If this is not already running, select Monitor Tomcat from the start menu. You may need to right-click and select Run As Administrator. Right-click on the taskbar icon and select Configure. Select the Java tab, and make sure that Use default is checked.		If you upgrade Java, make sure that Tomcat is reconfigured to use the new version. The simplest way to do this is through the Tomcat Control Panel. If this is not already running, select Monitor Tomcat from the start menu. You may need to right-click and select Run As Administrator. Right-click on the taskbar icon and select Configure. Select the Java tab, and make sure that Use default is checked.
		+

	=== Make a copy of the PINsafe files ===		=== Make a copy of the PINsafe files ===
Line 64:		Line 68:
	Specifically the files you will need are:		Specifically the files you will need are:

-	<path to Tomcat>\webapps\pinsafe\WEB-INF/conf/config.xml	+	<path to Tomcat>\webapps\pinsafe\WEB-INF\conf\config.xml
-	<path to Tomcat>\webapps\pinsafe\WEB-INF/conf/ranges.xml	+	<path to Tomcat>\webapps\pinsafe\WEB-INF\conf\ranges.xml
-	<path to Tomcat>\webapps\pinsafe\WEB-INF/data/repository.xml	+	<path to Tomcat>\webapps\pinsafe\WEB-INF\conf\config.properties
		+	<path to Tomcat>\webapps\pinsafe\WEB-INF\data\repository.xml

	* If using the database "Internal" you will need:		* If using the database "Internal" you will need:

-	<path to Tomcat>\webapps\pinsafe\WEB-INF/db	+	<path to Tomcat>\webapps\pinsafe\WEB-INF\db

	* If using an external database such as MySQL or MSSQL or Oracle, ensure you take a complete backup of the database		* If using an external database such as MySQL or MSSQL or Oracle, ensure you take a complete backup of the database
Line 79:		Line 84:

	* If the Internal, or MySQL DB is not being used, backup the DB driver file you are using from <path to Tomcat>\webapps\pinsafe\WEB-INF\lib		* If the Internal, or MySQL DB is not being used, backup the DB driver file you are using from <path to Tomcat>\webapps\pinsafe\WEB-INF\lib
		+

	=== Remove the old instance of PINsafe ===		=== Remove the old instance of PINsafe ===
Line 91:		Line 97:

	* If the pinsafe folder has not completely gone, stop Tomcat, delete the folder and then restart Tomcat.		* If the pinsafe folder has not completely gone, stop Tomcat, delete the folder and then restart Tomcat.
		+

	=== Install a new instance of PINsafe ===		=== Install a new instance of PINsafe ===
Line 105:		Line 112:

	* Stop Tomcat		* Stop Tomcat
		+

	=== Copy configuration and data files ===		=== Copy configuration and data files ===
Line 121:		Line 129:

	* Start Tomcat, pinsafe will startup and begin to upgrade the database configured in the config.xml		* Start Tomcat, pinsafe will startup and begin to upgrade the database configured in the config.xml
		+

	== Testing ==		== Testing ==