SQL connectivity security - Revision history

ELowell at 00:00, 12 October 2016

2016-10-12T00:00:44Z

← Older revision		Revision as of 00:00, 12 October 2016
Line 140:		Line 140:
	For more information about SQL security user exits, see the [[SQL security exits]] topic.</p>		For more information about SQL security user exits, see the [[SQL security exits]] topic.</p>

			==See also==
			{{Template:SQL connectivity topic list}}

	[[Category: SQL connectivity]]		[[Category: SQL connectivity]]

JAL: link repair

2015-08-17T19:44:48Z

link repair

← Older revision		Revision as of 19:44, 17 August 2015
Line 56:		Line 56:
	<ul>		<ul>
	<li>		<li>
	LOGIN and GUESTUSER parameters of the <var>[[DEFINE PROCESSGROUP ~~command\|DEFINE PROCESSGROUP]]~~</var> command</li>		LOGIN and GUESTUSER parameters of the <var>DEFINE PROCESSGROUP</var> command</li>
	<li>		<li>
	Model 204 <var>[[SYSOPT parameter\|SYSOPT]] parameter</var></li>		Model 204 <var>[[SYSOPT parameter\|SYSOPT]] parameter</var></li>
Line 92:		Line 92:
	<p class="caption">Login security processing decision tree</p>		<p class="caption">Login security processing decision tree</p>
	<p class="figure">[[File:SQL_Connect_Guide_fig_6-2.gif]]</p>		<p class="figure">[[File:SQL_Connect_Guide_fig_6-2.gif]]</p>

	===Trusted login ===		===Trusted login ===
	The LOGIN and GUESTUSER parameters offer extensions to Model 204 login security. If you trust that a client node reliably verifies the validity of its users, you can define the node to be either:		The LOGIN and GUESTUSER parameters offer extensions to Model 204 login security. If you trust that a client node reliably verifies the validity of its users, you can define the node to be either:
Line 127:		Line 128:
	==Client system security==		==Client system security==
	In general, follow the security procedures outlined in the documentation for your client system's operating system.		In general, follow the security procedures outlined in the documentation for your client system's operating system.
	<p>The system manager of the client system must also use the Model 204 DEFINE PROCESSGROUP and DEFINE PROCESS commands to define the server systems and programs with which the client can communicate.</p>		<p>
			The system manager of the client system must also use the Model 204 <var>DEFINE PROCESSGROUP</var> and <var>DEFINE PROCESS</var> commands to define the server systems and programs with which the client can communicate.</p>

	==SQL security user exits==		==SQL security user exits==

ELowell: /* Known user ID */

2015-07-20T19:52:24Z

Known user ID

← Older revision		Revision as of 19:52, 20 July 2015
Line 103:		Line 103:
	Users from the node can then be logged in for SQL Server access without having to present a password.</p>		Users from the node can then be logged in for SQL Server access without having to present a password.</p>
	====Known user ID====		====Known user ID====
	A user from a trusted node must have a known user ID but no password to be logged in successfully. A<i>known user ID</i> is one that is defined in either the Model 204 password table (CCASTAT) or in CA-ACF2.		A user from a trusted node must have a known user ID but no password to be logged in successfully. A <var class="term">known user ID</var> is one that is defined in either the Model 204 password table (CCASTAT) or in CA-ACF2.
	<p>		<p>
	If a user ID is not defined in CCASTAT but is defined in Security Server (formerly RACF) or CA-Top Secret, it is considered unknown. Horizon gives the trusted user the login user privileges defined for their user ID.</p>		If a user ID is not defined in CCASTAT but is defined in Security Server (formerly RACF) or CA-Top Secret, it is considered unknown. Horizon gives the trusted user the login user privileges defined for their user ID.</p>

ELowell: /* Model 204 login security */

2015-07-20T19:51:35Z

Model 204 login security

← Older revision		Revision as of 19:51, 20 July 2015
Line 56:		Line 56:
	<ul>		<ul>
	<li>		<li>
	LOGIN and GUESTUSER parameters of the DEFINE PROCESSGROUP command</li>		LOGIN and GUESTUSER parameters of the <var>[[DEFINE PROCESSGROUP command\|DEFINE PROCESSGROUP]]</var> command</li>
	<li>		<li>
	Model 204 SYSOPT parameter</li>		Model 204 <var>[[SYSOPT parameter\|SYSOPT]] parameter</var></li>
	</ul>		</ul>

ELowell: /* Process definition */

2015-07-20T19:49:41Z

Process definition

← Older revision		Revision as of 19:49, 20 July 2015
Line 38:		Line 38:

	===Process definition===		===Process definition===
	For a given server program (application subsystem or procedure) to be accessible from any client system, the server system manager must include the name of a processgroup that defines that client system in the FROM parameter of the server program's [[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]] command.		For a given server program (application subsystem or procedure) to be accessible from any client system, the server system manager must include the name of a processgroup that defines that client system in the FROM parameter of the server program's <var>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]]</var> command.
	<p>The system manager is thus required to tell Model 204 explicitly which nodes in the network can access any server program.</p>		<p>The system manager is thus required to tell Model 204 explicitly which nodes in the network can access any server program.</p>

ELowell: /* Processgroup definition */

2015-07-20T19:49:19Z

Processgroup definition

← Older revision		Revision as of 19:49, 20 July 2015
Line 33:		Line 33:

	===Processgroup definition===		===Processgroup definition===
	For a client system to establish a TCP/IP session with a Model 204 server, the client's network node name must be coded in the REMOTEID parameter of a server's [[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|		For a client system to establish a TCP/IP session with a Model 204 server, the client's network node name must be coded in the REMOTEID parameter of a server's <var>[[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|
	DEFINE PROCESSGROUP]] command.		DEFINE PROCESSGROUP]]</var> command.
	<p>Because this command requires system manager privileges, a given client system must be specifically authorized by a server's system manager to gain access to the server.</p>		<p>Because this command requires system manager privileges, a given client system must be specifically authorized by a server's system manager to gain access to the server.</p>

ELowell at 17:27, 23 February 2015

2015-02-23T17:27:10Z

← Older revision		Revision as of 17:27, 23 February 2015
Line 139:		Line 139:


	[[Category: SQL ~~Connectivity~~]]		[[Category: SQL connectivity]]

ELowell at 23:20, 20 February 2015

2015-02-20T23:20:47Z

← Older revision		Revision as of 23:20, 20 February 2015
Line 139:		Line 139:


	[[Category: ~~Model 204 SQL processing\|~~SQL Connectivity]]		[[Category: SQL Connectivity]]

ELowell at 23:18, 20 February 2015

2015-02-20T23:18:26Z

← Older revision		Revision as of 23:18, 20 February 2015
Line 139:		Line 139:


	[[Category: Model 204 SQL processing]]		[[Category: Model 204 SQL processing\|SQL Connectivity]]

ELowell at 20:28, 20 February 2015

2015-02-20T20:28:11Z

← Older revision		Revision as of 20:28, 20 February 2015
Line 137:		Line 137:
	<p>		<p>
	For more information about SQL security user exits, see the [[SQL security exits]] topic.</p>		For more information about SQL security user exits, see the [[SQL security exits]] topic.</p>


			[[Category: Model 204 SQL processing]]