AllTechGuide - BETA

[...] encryption key in both the environments, I planned to export and import the objects in clear text. As a first step, I exported my r6 policy objects using the below command smobjexport - [...]

[...] This document focuses on some of the order discount proration issues we encounter, when we pass the order details to the fulfillment systems. I [...]

[...] default values for each query field correspond to the SiteMinder sample relational database schema called SmSampleUsers. Customers must modify these queries according to their database [...]

[...] -step fix for the syntax error. Source your environment variables script. Run the Policy Server Configuration Wizard. You do not have to configure your policy store/webserver/oneview monitor again. [...]

[...] for authentication. Since the user inputs phone number for authentication, your Authenticate User query will look something like this- SELECT UID FROM table1 WHERE UID = (SELECT UID FROM [...]

[...] configuration, you have configured UID as your universal id, DisabledState as your DisabledState User inputs the phone number to authenticate and not the UID. With the above assumptions in [...]

[...] relationship, meaning a user can be associated with one or many phone numbers. In the User Directory configuration, you have configured UID as your universal id, DisabledState as your DisabledState [...]

[...] the phone number. So our queries will look like this at runtime. SELECT UID, DisabledState FROM table1 where UID = (SELECT UID FROM table2 WHERE PhoneNumber = ‘myusername’) SELECT [...]

[...]  second %s value is always the value the user inputs for authentication. Since the user inputs phone number for authentication, your Authenticate User query will look something like this- [...]

[...] out a key difference in the way the query “Get User Property” is executed by the SiteMinder policy server in versions 12.0 and 12.51. This is important for customers who are planning an [...]