Set user security in the CICS TS region
在CICSTS区域设置用户安全性
Set user security in the TXSeries region.
在TXSeries区域设置用户安全性。
Local OS registry (other operating systems) : user security name.
本地OS注册中心(其他操作系统)：用户安全名称。
Custom registry with "use display name" false: user security name.
“Usedisplayname”为false的自定义注册中心：用户安全名称。
In the next section we set up user security over IP connectivity with SSL.
下一节我们将使用经ssl加密的IP连接建立用户安全性。
The user security of application programs is one of important subjects in MIS.
应用程序用户安全性是MIS系统开发的重要部分之一。
This requires controlling user security and permissions for testing members and artifacts.
这需要对测试人员和工件控制用户安全和进入许可。
Figure 5 shows summarizes the attributes needed to set up user security between CICS TS and TXSeries.
图5总结了在CICSTS与TXSeries之间建立用户安全性所需的属性。
For user security, you need to set the following resource definitions for IPIC connections in CICS ts.
对于用户安全性，您需要在CICSTS中为IPIC连接设置以下资源定义。
The transfer and assertion of the current task’s user security context between address spaces is among these.
其中还包括在地址空间之间传输和断言当前任务的用户安全上下文。
Maxium user security through snap-lock functionality & red-colour indications for open and closed position.
最大用户的安全，通过管理单元打开和关闭位置锁定功能的红色标志。
Specify the level of user security for inbound requests only, on the USERAUTH attribute of the IPCONN resource definition.
在IPCONN资源定义的USERAUT h属性上，仅为入站请求指定用户安全级别。
In order to guarantee user security, offered to you on this site to download the file anti-virus, and updated anti-virus software.
为了保证用户安全，请主动为您在本网站下载的文件杀毒，并及时更新杀毒软件。
These include changing the owner of a mail database, changing passwords, setting up user security, customizing replication Settings, and so on.
这些包括更改邮件数据库的拥有者、更改密码、设置用户安全性、定制复制设置等。
IDSLBACREADSET: Each set component of the user security label must include the set component of the data security label to allow access to data.
IDSLBACREADSET：要访问数据，用户安全标签的每个集合组件必须包括数据安全标签的集合组件。
IDSLBACWRITESET: Each set component of the user security label must include the set component of the data security label to allow access to data.
IDSLBACWRITESET：要访问数据，用户安全标签的每个集合组件必须包括数据安全标签的集合组件。
They want to balance the desire to be on the front edge of access to the Indian market, with the collateral impact of compromising user security.
他们希望平衡在印度电信市场中保持强劲竞争力的需求，及为了进入这个市场而必要的在用户通讯安全性方面的牺牲。
IDSLBACWRITEARRAY: Each array component of the user security label must be equal to the array component of the data security label to allow access to data.
IDSLBACWRITEARRAY：要访问数据，用户安全标签的每个数组组件必须等于数据安全标签的数组组件。
To allow for ease of use, wireless Hosted Network also supports the concept of a secondary or user security key that is more user-friendly, but could be less secure.
为了便于使用，无线承载网络还支持“第二密钥”，也称作“用户安全密钥”，使用起来更加友好，但是安全性稍差。
IDSLBACREADARRAY: Each array component of the user security label must be greater than or equal to the array component of the data security label to allow access to data.
IDSLBACREADARRAY：要访问数据，用户安全标签的每个数组组件必须大于或等于数据安全标签的数组组件。
For example, for a queue, an MQQUEUE profile is used to control MQI access to the queue, but other profiles in the MQADMIN class are used to control context and alternate user security.
例如，对于队列，使用一个MQQUEUE概要文件来控制对该队列的访问，但是mqadmin类中的其他概要文件用于控制上下文和用户安全性。
Similar to context security, if you do not plan to use alternate user security, define a backstop profile (CSQ1.ALTERNATE.USER.**) with a UACC of NONE and do not grant any users access to it.
与上下文安全性类似，如果您不打算使用替代用户安全性，那么可以定义一个UACC 为NONE 的backstop配置文件（CSQ1.ALTERNATE.USER.**），且不要向它授予任何用户访问权。
Mappings are created for the user roles in the user security registry, then imported into Modeler, so that any design to deploy processes can properly assign work to users in the test environment.
为用户安全注册中心的用户角色创建映射，然后导入Modeler，以便任何“为部署而设计”流程能够在测试环境中为用户正确分配工作。
These policies are policies integrated of system security, data security and user security, and introduce the authentication of Database, exterior, enterprise and user and the permission res.
进一步地介绍了数据库验证、外部验证、企业验证和并发许可等用户验证和许可限制。
This brings up a few questions: What if a malicious user hacks the underlying security mechanism itself?
这会带来几个问题：如果恶意用户攻破了底层安全机制本身，那么会怎么样？
The solution presented in this article is a loosely-coupled user role security integration solution.
本文提出的解决方案是一种松耦合的用户角色安全集成解决方案。
Some people suggest using random passwords for ordinary user accounts is good security policy.
一些人认为对于普通用户账户使用随机密码是良好的安全策略。
This secret key is known only to the user and the security server.
此秘密密钥只有该用户和安全服务器知道。
Manage user interface security.
管理用户界面安全。
Then one can gradually lift the security of that user as your security policy demands.
以后可以根据安全策略的要求逐渐放松此用户的安全限制。
应用推荐