CUP 5.3 - Single Sign On fu00FCr end user request screen?

Hi everyone,
Is there any way to achieve Single Sign On in a windows environment using the corporate Active Directory for the END USER REQUEST SCREEN in CUP 5.3?
I am aware of the document "Single Sign-On with SAP BusinessObjects Access Control 5.3" by the SAP GRC RIG (Harleen Kaur) so I know how to achieve Single Sign On for the CUP application itself.
I am also aware of the option to deactivate "end user verification required" in the authentication source definition in CUP.
What our end users are asking for is true single sign on. They would like to enter a request WITHOUT providing network user ID and/or password manually.
Thanks!

Hi Raghu,
Thanks a lot!
We have not yet configured SSO but are in the phase of analyzing our options.
I understood that SSO is only possible for the server:port//AE/index_apr.jsp page in CUP.
What about the end user request screen (server:port/AE)? Will this work with Windows-SSO using SPNEGO? Would I set the authentication source to LDAP or to UME (UME has multiple LDAP as user data source)?
Many thanks and best regards
Patrick

Similar Messages

Customizing labels in end user request screen

Hello everyone,
Is it at all possible to customize the labels for various languages in the end user request screen?
I would have assumed those labels were maintained in the "initial system data" files, but they are not.
Specifically, we are trying to change the label "User ID" to "SAP User ID" to make it clear for our end users which user ID this field refers to.
Thanks!

Hi Patrick,
It is not possible to change the filed label name. However, in GRC 10 I infer that End User Personalization (EUP) templates are available that allows you to customize.
Regards,
Raghu

Active Directory, single sign-on and SRM Users

We are in the process of installing SRM 7.0. using the Classic Scenario. I am seeking clarification around the creation of users in that system given the following:
- My Basis colleagues are in the process of implementing single sign-on using Active Directory for our SAP Portal, SAP Business Warehouse and SRM systems.
- Single sign-on will not at this point be used for our SAP ECC 6.0 system
My questions are:
1. If active directory is being used do we need to create actual users within the SRM system?
2. If actual users in the SRM system are not required, does this have any impact on the creation of the Organizational structure in SRM from the SAP ECC HR hierarchy?
Many Thanks

Hi Claire,
The Single Sign On work only if user exist on every systemes.
For example :
If you connect trough portal to access ECC and SRM, your user id must exist in ECC and SRM.
For Active Directory you can synchronize your user table to AD by using LDAP option.
The best way is to configure a CUA for ECC and SRM, use the UME of Portal on ECC and synchronize the CUA to Active Directory.
Finally use the SSO certificate between Portal ECC and SRM.
Regards,
Gilles SEBBAG
Sap Technical Consultant.

Let end user request a role

I want my end users to be able to request roles for themselves.
Is there a out-of-the-box way to do this, or do I have to implement it myself?
If I have to do it myself, please point me in the right direction.
Thanks in advance
Stefan

Hi,
Thnk u for u r quick reply.....
i am using... IDM8.1
I will Expain u the problem clearly...
I created an ITRole(IT1) and assigned AD as optional resource.After tht i created Business role(B1) and assigened the ITRole(IT1) to tht roleB1.I assigned the B1 to the user . But i observed tht the resource(AD) is not Assigned to the user.So my question is how to assign the AD to tht user..one more surprising thing is the AD resource is not there in the user's available resources list also(End user and Admin interfaces).Am i doing anything wrong??
Tnx in advance......
Regards,
Kavitha

End User Personalization - Mandatory field does not make it mandatory

I am on GRC 5.3 SP8 and when I set "Company" as "Mandatory" under "End User Personalization", it does not put an "*" next to Company or force the user to fill in the Company field.
How can I make sure that the user enters "Company" when doing a "Create Request form"? I want to make sure a red "*" is next to the field so that they update it. Right now I have a default value in there but I want to make sure they think about what goes in this field.
When I create a custom field and use "end user personalization", the red "*" shows up and an error occurs if they don't fill in the field, but the predefined fields don't work the same way.
Thanks,
Peggy

GRC Experts, please correct me if I'm wrong but from my understanding, the Request Screen in the MyWork tab is for Approvers/Admins/Security i.e. those with UME permissions of some kind. This is not the Request Screen for end users. We actually customize our UME roles to elimate the ability to use this Request Screen. We want all of our security requests to be done in the End User Request Screen.
Unlike the MyWork Request Screen, the End User Request Screen is customizable under configuration-->End User Personalization. As you've noticed, here you can customize what fields you see on the End User Request Screen, what fields are defaulted, etc. For example, for our company, we do not want end users picking and choosing roles. Our end users are not knowledgable on our roles so we save that step for a stage in which Security Admins choose roles for users based on what they asked for in the Request Reason.
Another advantage of using the End User Request Screen is that end users can create requests without having UME permissions; they need only to be authenticated against whatever system you have chosen to authenticate them against (for example, SAP) Configuration-->Authentication. As long as they exist in that system, they can create a request.
Every company is different. For us, we don't like that the MyWork Request Screen is not customizable and requires UME permissions to even access it. So we have essentially taken it away through security (based on the Security Guide provided by SAP).

GRC AC CUP 5.3 SP06: Single Sign-On

Has anyone gotten single sign-on with Compliant User Provisioning to work? I've got my java stack authenticating kerberos tickets through SPNEGO with LDAP as the user data source. It works fine on every other application (RAR, SPM, ERM) except for CUP, which requires users to login. Is there anyway to force single sign-on inside of CUP or will my users always be required to type in their passwords for requesting and approving access?

Daniela,
Thank you, that's exactly what I was looking for, but I'm currently getting an error stating the following:
Application error occurred during request processing.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalArgumentException: Cannot redirect to "null" location.
My redirection URL looks like this:
http://<server>:<port>/RedirectApp/?redirecturl=http://<server>:<port>/AE/index.jsp
Does that look right? What support pack were you able to get this working on?

Oracle Application Single Sign-On

Dear All,
We have a requirement that there should be single sign-on for the users to use both the Oracle and non-Oracle Applications. We are using Oracle Application Server 10g at the back end.
How to enable single sign-on. Is there any tool that we need to install.
Pls guide us as we are entirely new to this process.
Regards,
Rajani

Hi,
You need to install and configure Oracle Internet directory and Single Sign On compontents of Oracle Application server 10g in order to have the Single Sign On working with Oracle Applications. After the Oracle Application Server Infrastructure tier installation there is addition integration steps you need to follow to integrate the Single Sign on with Oracle E-business suite. You can use DIP features ( Directory Integration and Provisiotion) to integrate with Third party directory server like Micrososft AD, Sun directory server etc. for Integrating the non oracle based application i think you have to use oracle single sign on API and you need to do bit of coding as well. You can also enble single sign on for database users but this requires advance security option enabled on the Database side and finally you can integrate Single sign on for OS users as well.
Raj

Single sign-on and different usernames and passwords

Hello,
I am building a Portal with WLPS 3.5 and WLS 6.0. I tried to get
information about the background of single sign-on.
I understand, that I need a Realm (i.e. LDAP Realm) to authenticate the
user for the first login to the portal (with username and password).
Now I would like to integrate my webmail-programm (to get emails from
Lotus Notes via Internet) as a portlet.
For my understanding the user has to authorizate to get access to webmail.
Therefore I create a ACL for webmail and this ACL is assigned to my
security Realm.
I would like the portlet to show after login the number of mails for the
specific user. But where are the username and password for webmail stored
and how are they received and forwarded?
I understand that my ACL included all users that have access to webmail
(i.e. all users). But I only want emails for the specific user.
Does WLS get all usernames and passwords while the first login? Do I have to
implement a algorithmen to get the specific username and password for the
requested resource in my portlet?
Has anyone solved a similar problem or can tell me where I can get more
information. I read the WebLogic Security document but I cant find a
answer to my questions.
Thanks
Lydia

Lydia,
I'm not an expert in this area, but I can give you a start.
As for single sign-on, there are different levels. For single sign-on across web-apps,
the servlet spec requires this (section 12.6 of th 2.3 spec) and therefore Weblogic
does this.
What you are talking about is single sign-on across back-end applications through
a web-app. BEA has partnered with Securant (just acquired by RSA) to provide this
kind of functionality. Browse to http://www.rsasecurity.com/products/ and look
at the ClearTrust product. BEA has also partnered with Netegrity (www.netegrity.com)
with their SiteMinder product. Neither is included in the Weblogic license. I'm
sure either vendor would be excited to explain how their product will solve your
problem if you give them a call.
As for where the username and passwords are stored, that is up to the realm. If
you are using the default WLPS RDBMSRealm, the username and encrypted password
are stored in the WLCS_USER table. If you are using LDAPRealm, they are stored
in your LDAP server.
Hope this was useful!
PJL
[email protected] wrote:
Hello,
I am using PersonalizationServer 3.5 and WLS 6.0 SP 2.
Now I try to unterstand the functionality of Single sign-on when a user
has different usernames and passwords for different applications.
Can someone explain where the usernames and passwords for a user are
stored (all in the LDAP-realm or a RDBMS-realm?) When a user access the
application how username and passwords are mapped? Or usernames and
passwords for all applications are the same and will be equalized?
Precisely I would like to get access to a mail-account for a specific
user
(webmail from Lotus Notes).
Thanks for any help
Lydia

Multiple and single sign on

Hi Experts,
Could you please give info on Multiple and single sign on directory settings ?
Regards
Sara

hi sara,
have a look on this also. u can get better idea on sign on's
this is a very deep document.............
reward me points if its usefull.................dont forget
Single Sign-On in SharePoint Portal Server 2003
This is a sample chapter from the Microsoft SharePoint Products and Technologies Resource Kit. You can obtain the complete resource kit (ISBN 0-7356-1881-X), which includes a companion CD-ROM, from Microsoft Press.
Single sign-on is a new feature in Microsoft Office SharePoint Portal Server 2003 that provides storage and mapping of credentials such as account names and passwords so that the portal sitebased applications can retrieve information from the third-party applications and back-end systems, for example, Enterprise Resource Planning (ERP) and Customer Relations Management (CRM) systems. The single sign-on functionality is implemented by the Microsoft Single Sign-On (SSOSrv) service. SSOSrv is a credential storage service that allows the saving and retrieval of credentials. The use of single sign-on functionality stops users from having to authenticate themselves more than once when the portal sitebased applications need to obtain information from other business applications and systems.
In a single sign-on environment, these back-end applications and systems are referred to as enterprise applications. To enable customers to interact with an enterprise application directly from the portal site, SharePoint Portal Server 2003 stores and maps assigned credentials within an enterprise application definition. By using application definitions, you can automate, and secure the sign-on process to the corresponding enterprise applications from a portal sitebased application.
The single sign-on functionality enables scenarios where multiple Web Parts access different enterprise applications, which each use a different type of authentication. Each Web Part can automatically sign on to its enterprise application without prompting the user to provide credentials each time. There are endless uses of single sign-on functionality within an enterprise environment. For example, lets consider two different scenariosa human resources intranet site and a business intelligence site, as follows:
     A standard human resources (HR) portal site or page might include several Web Parts that display employee information from a back-end employee management system. This employee data is stored in a dedicated HR database system, frequently based on SAP or PeopleSoft. These HR databases do not support Microsoft Windows IDs, might not run on Windows-based operating systems and, in fact, might include proprietary logon protocols. The Web Parts on the portal site should retrieve the individual employee data without prompting for a separate logon. In this example, the individual employee does not have a separate logon to the HR system, but uses a group account that provides generic read access to the database. In other words, the employee does not know the user name and password required to log on to the system he or she is accessing.
     An executive might use a portal site to provide a dynamic, aggregated view of relevant business information. This data is stored in two places: Siebel stores the customer relationship information, and SAP tracks accounts and payments. To see an integrated view, the portal must log on to and access both back-end systems. Prompting the user for additional passwords is an unacceptable user experience. In this example, the executive does not need to know the user names and the passwords required for logon to the back-end systems. In addition, multiple Web Parts are used to ensure this integration. By default, each Web Part separately authenticates the user to the appropriate back-end system.
As these examples show, by using single sign-on you can centralize information from multiple back-end applications through a single portal that uses application definitions. In addition, SharePoint Portal Server 2003 provides a programming interface for developers to use and extend this feature.
Single Sign-On Architecture
For each enterprise application that SharePoint Portal Server connects to, there is a corresponding enterprise application definition configured by an administrator. This application definition is used by a Web Part to integrate with the enterprise application within a portal site. The application definition controls how credentials for a particular business application are stored and mapped. The code within the Web Part uses the application definition to retrieve credentials that are then used to integrate with an enterprise application. This process is transparent to the portal site users.
There are two primary types of enterprise application definitions used with the SSOSrv service, as follows:
Individual enterprise application definitions.
     In this scenario, individual users know and can manage their own credentials stored within the enterprise application definition.
Group enterprise application definitions.
     In this scenario, the individual user does not know his or her credentials stored within the enterprise application definition, but is associated with a managed group account.
The single sign-on administrator, rather than the individual user, chooses the account type when configuring the enterprise application definition.
The SSOSrv service stores encrypted credentials in a Microsoft SQL Server database. When you set up the single sign-on on the job server, you specify two settings for the single sign-on database: the name of the computer running SQL Server where the credentials store will be located, and the name of the database that will become the credentials store for your Web farm. These settings are stored in the SharePoint Portal Server configuration database.
All credentials in the credentials store are encrypted using the single sign-on encryption key. When you configure single sign-on for the first time, the encryption key is created automatically. You can regenerate the key if required and re-encrypt the credentials store; for example, you might have a policy to change the key after a certain amount of time.
How Single Sign-On Works
When individual enterprise definition is used, on the first access to the Web Part that integrates with the enterprise application, if a users credentials have not been stored in the single sign-on database, the user is redirected to the logon form that prompts the user for appropriate credentials for the enterprise application. The number, the order, and the names of the fields in the logon form are configured by the administrator within the application definition; the logon form is generated automatically based on these configuration settings. The developer needs to write the code within the Web Part to check whether the credentials exist in the database, and to redirect the user to the logon form if necessary. The user-supplied credentials are then stored in the credentials store and mapped to the Windows account that is this users account for SharePoint Portal Server. Then, the user is redirected back to the original Web Part. The code in the Web Part then submits the credentials from the credentials store to the application in the way that is relevant to this application, and retrieves the necessary information that is then presented to the user within the Web Part. This process is shown in Figure 26-1. The steps are as follows:
     1.     A user accesses the Web Part that integrates with the enterprise application for the first time. The Web Part code checks whether the user credentials for the required application are stored in the single sign-on database. If they are stored, the process continues from step 6 in this list.
     2.     If there are no credentials stored for this user for the required application, the users browser is redirected to the logon form for this application.
     3.     The user supplies credentials for the application.
     4.     The supplied credentials are mapped to the users Windows account and stored in the single sign-on database.
     5.     User is redirected to the original Web Part.
     6.     The Web Part retrieves the credentials from the single sign-on database.
     7.     The Web Part submits the credentials to the enterprise application and retrieves the necessary information.
     8.     The Web Part is displayed to the user.
On subsequent access, when the user requests the Web Part, to get the necessary data from the enterprise application the credentials are retrieved from the single sign-on database. The process is transparent to the user. (See Figure 26-1.)
Figure 26-1. Accessing an enterprise application using single sign-on
When group enterprise definition is used, the account mapping is configured by the administrator. The administrator specifies the credentials for accessing the enterprise applications that are valid for all members of a Windows group. If the user who accesses the Web Part belongs to the mapped Windows group, the access credentials are already stored in the single sign-on credentials store. The code in the Web Part retrieves the credentials, submits them to the enterprise application, and retrieves the necessary information. The Web Part is then displayed to the requesting user. In this scenario, the whole process is transparent to the user. The user is not aware of any authentication information required for the enterprise application; it is only known to the administrator.
Security Recommendations Regarding the Topology of the Server Farm
When using the single sign-on service, you can help enhance security by distributing your resources in the server farm. Specifically, the configuration of the front-end Web server, the job server, and the computer storing the single sign-on database can affect security.
Less secure configuration.
     Everything is deployed on one server. This configuration is less secure because the front-end Web server, the single sign-on database stored in SQL Server, and the encryption key are on the same computer. This configuration is not recommended.
More secure configuration.
     Two-computer configuration where one computer is the front-end Web server. The second computer is the job server containing the single sign-on database stored in SQL Server and the encryption key.
Recommended configuration for better security.
     Configuration of three or more computers in which the front-end Web server, the job server containing the encryption key, and the server containing the single sign-on database stored in SQL Server are different computers.
If you are using single sign-on in a shared services scenario, the user credentials stored in the parent server farm are available to the administrators of all child server farms. It is recommended that you run applications using single sign-on on the parent portal site only and use an iFrame in the application for child portal sites. You should disable the single sign-on service on child server farms. We will discuss how to disable the SSOSrv service later in this chapter.
Configuring Single Sign-On
To configure single sign-on for the first time, you must complete the following tasks:
     1.     Determine and set up necessary Windows accounts.
     2.     Enable the single sign-on service on the job server.
     3.     Configure the single sign-on settings.
     4.     Create a new application definition.
     5.     Provide account information for the application definition.
     6.     Enable the single sign-on service on the front-end servers.
Step 1: Set Up Single Sign-On Accounts
The SSOSrv service uses the following four types of accounts:
     Configuration account for single sign-on
     Single sign-on administrator account
     Single sign-on service account
     Enterprise application manager account
Before configuring single sign-on, you must determine and, where necessary, create and set up these accounts.
Configuration Account for Single Sign-On
Configuration Account for single sign-on is the Windows account that will be used to configure the SSO. When setting up single sign-on, you use this account to log on to the job server. This account must meet the following requirements:
     Be a member of the local Administrators group on the job server.
     Be a member of the local Administrators group on the computer running SQL Server that stores the single sign-on database.
     Be either the same as the single sign-on administrator account, or be a member of the group account that is the single sign-on administrator account. (The single sign-on administrator account is discussed in the next section.)
Single Sign-On Administrator Account
The single sign-on administrator account can be either the Windows Global group or the individual user account, and it will be used to set up and manage the single sign-on service. This account cannot be a local domain group account or a distribution list.
Make sure that the following requirements are met for the single sign-on administrator account:
     The single sign-on service account must be this user or a member of this group.
     The configuration account for single sign-on must be this user or a member of this group.
We will specify this account as the single sign-on administrator account in step 3, Configure the Single Sign-On Settings on the Job Server. After it has been configured, this user account or members of this group account will have full access to the single sign-on administration pages and will be able to make configuration and application definition changes.
Single Sign-On Service Account
The single sign-on service account is the user account that will run as the single sign-on service. Make sure the following requirements are met:
     The single sign-on service account must be the same as the single sign-on administrator account or a member of the group account that is the single sign-on administrator account.
     The single sign-on service account must be a member of the local group STS_WPG on all servers running SharePoint Portal Server 2003 in the server farm.
To make the user a member of STS_WPG, do the following:
     1.     On the taskbar, click Start, point to Administrative Tools, and then click Computer Management.
     2.     In the console tree, under the System Tools node, expand the Local Users and Groups node.
     3.     Click Groups.
     4.     Double-click STS_WPG.
     5.     In the STS_WPG Properties dialog box, click Add.
     6.     Add the user.
The single sign-on service account must be a member of the local group SPS_WPG on all servers running SharePoint Portal Server in the server farm.
To make the user a member of SPS_WPG, do the following:
     1.     On the taskbar, click Start, point to Administrative Tools, and then click Computer Management.
     2.     In the console tree, under the System Tools node, expand the Local Users and Groups node.
     3.     Click Groups.
     4.     Double-click SPS_WPG.
     5.     In the SPS_WPG Properties dialog box, click Add.
     6.     Add the user.
The single sign-on service account must be a member of the public database role on the SharePoint Portal Server configuration database.
   On a single server deployment, if the single sign-on service runs under an account that is a member of the local Administrators group, you do not need to ensure that the user has the public right on the configuration database. However, for security reasons it is recommended that you do not run the service under an account that is a member of the local Administrators group.
To assign rights on the configuration database, do the following:
     1.     On the SQL Server computer, open SQL Server Enterprise Manager.
     2.     Expand the Microsoft SQL Servers node.
     3.     Expand the SQL Server Group node.
     4.     Expand the (local) (Windows NT) node.
     5.     Expand the Security node.
     6.     Click Logins, and then do one of the following:
7.               If the logon name does not exist, right-click Logins, click New Login, and then in the Name box, type the account for the user in the format DOMAIN\user_name.
8.               If the logon name already exists, right-click the logon name, and then click Properties.
     7.     Click the Database Access tab.
     8.     In the Specify which databases can be accessed by this login section, select the check box for the configuration database.
     9.     In the Database roles for database_name section, select the public check box.
     10.     Click OK.
     11.     Close SQL Server Enterprise Manager.
The single sign-on service account must be a member of the Server Administrators server role on the SQL Server instance where the single sign-on database is located.
   On a single server deployment, if the single sign-on service runs under an account that is a member of the local Administrators group, you do not need to ensure that the user is a member of Server Administrators server role on the SQL Server instance where the single sign-on database is located. However, for security reasons, it is recommended that you do not run the service under an account that is a member of the local Administrators group.
To make the user a member of the Server Administrator role
     1.     On the SQL Server computer, open SQL Server Enterprise Manager.
     2.     Expand the Microsoft SQL Servers node.
     3.     Expand the SQL Server Group node.
     4.     Expand the (local) (Windows NT) node.
     5.     Expand the Security node.
     6.     Click Logins, and then do one of the following:
               If the logon name does not exist, right-click Logins, click New Login, and then in the Name box, type the account for the user in the format DOMAIN\user_name.
               If the logon name already exists, right-click the logon name, and then click Properties.
     7.     Click the Server Roles tab.
     8.     Select the Server Administrators check box.
     9.     Click OK.
     10.     Close SQL Server Enterprise Manager.
Enterprise Application Manager Account
The enterprise application manager account can be the Windows Global group account, or individual user account, that will be used to set up and manage application definitions. This account cannot be a local domain group or a distribution list.
You do not need to perform any configuration steps now; we will configure this account to become the enterprise application manager account in step 3, Configure the Single Sign-On Settings on the Job Server. However, it is useful to notice the rights that this account will have after it has been specified as the enterprise application manager account, as follows:
     This account or members of this group have rights to create, modify, or delete application definitions from the single sign-on administration pages.
     This account or members of this group do not have rights to configure single sign-on. Only members of the single sign-on administrator account can configure single sign-on.
     Rights that this user or members of this group have are automatically contained in the single sign-on administrator account.
Step 2: Enable the Single Sign-On Service on the Job Server
To enable the SSOSrv service, do the following on the job server:
     1.     On the taskbar, click Start, point to Administrative Tools, and then click Services.
     2.     On the Services management console, double-click Microsoft Single Sign-on Service.
     3.     Click the Logon tab.
     4.     Under Log on as, click This account.
     5.     In the This account box, type an account name that you determined as a single sign-on service account in the previous step.
     6.     In the Password and Confirm password boxes, type the password.
     7.     Click Apply.
     8.     Click the General tab.
     9.     In the Startup type list, click Automatic.
     10.     In the Service status section, if the service status does not display Started, click Start.
     11.     Click OK.
Step 3: Configure the Single Sign-On Settings on the Job Server
To configure the single sign-on settings, you must be logged on as the configuration account on the job server. As we discussed earlier in step 1, Set Up Single Sign-On Accounts, this account must be a member of the local Administrators group on the job server, and must also be a member of the group account that you specify as the single sign-on administrator account.
You cannot configure single sign-on remotely. To configure single sign-on, go to the computer running as the job server, log on as the configuration account, and then do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Server Settings section, click Manage server settings.
     3.     On the Manage Server Settings for Single Sign-On page, in the Single Sign-On Settings section, in the Account name box, type the name of the single sign-on administrator account that you determined in step 1, Set Up Single Sign-On Accounts. The format of the account is DOMAIN\group_name or DOMAIN\user_name.
     4.     In the Enterprise Application Definition Settings section, in the Account name box, type the name of the enterprise application manager account that you determined in step 1, Set Up Single Sign-On Accounts. The format of the account is DOMAIN\group_name or DOMAIN\user_name.
     5.     In the Database Settings section, do the following:
6.          1.     In the Server name box, type the name of the database server on which you want to store the settings and account information for single sign-on.
2.          2.     In the Database name box, type the name of the single sign-on database.
If the database does not exist, it is created.
     6.     In the Time Out Settings section, do the following:
7.          1.     In the Ticket time out (in minutes) box, type the number of minutes to wait before allowing a ticket, or access token, to time out.
2.          2.     In the Delete audit log records older than (in days) box, type the number of days to hold records in the audit log before deleting.
     7.     Click OK.
     8.     If a message box appears stating that you have reconfigured single sign-on, click OK.
   The audit log is overwritten after the number of days you specify. Because the log contains a record of any illicit operations or logon attempts, it is recommended that you maintain backup copies of the logs. The logs reside in the single sign-on database in the SSO_Audit table. This table is automatically backed up when you back up the database.
Step 4: Create an Application Definition
To create an application definition, you need to be logged on as a member of single sign-on administrator account or as an enterprise application definition manager account. To create an application definition, do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Enterprise Application Definition Settings section, click Manage settings for enterprise application definitions.
     3.     On the Manage Enterprise Application Definitions page, click New Item.
     4.     On the Create Enterprise Application Definition page, in the Application and Contact Information section, do the following:
5.          1.     In the Display name box, type a display name for this application definition.
When administrator changes the settings for the application definition at a later stage, the application definition is listed using its display name.
The display name is what the user sees on the logon form when entering credentials on the first access.
   If you enter a long name with no spaces in it for the display name, the entire name might not be displayed.
2.          2.     In the Application name box, type an application name for the application definition. The application name is used by developers.
   If you enter a long name with no spaces in it for the application definition name, the entire name might not be displayed.
3.          3.     In the Contact e-mail address box, type an e-mail address for users to contact for this application.
     5.     In the Account Type section, do one of the following:
6.               If you want all users to log on by using a single account, select Group.
Users do not need to enter any credentials with this option.
7.               If you want users to log on by using their own account information, select Individual.
Each user will have to provide credentials when accessing the Web Part for the first time.
   If you specify a group account as the account type, so that all users log on by using a single account, ensure that you have the appropriate number of client licenses for the application that you are accessing.
     6.     In the Logon Account Information section, select one or more fields to map to the required logon information in the necessary order for this enterprise application. The number and the order of the fields are defined by the enterprise application logon requirements. For each field, do the following:
7.          1.     Type a display name for each field as a reminder of the required information. For an individual user application definition, the display name is what the users see on the logon form when entering their credentials for the enterprise application. For a group application definition, the display name of the field is what the administrator sees when entering the mapped group account credentials for the enterprise application.
2.          2.     If the field contains sensitive information, such as a password, click Yes for Mask so that the information is not displayed within this field when it is being filled in or viewed.
For example, for access to Oracle, you might enter the following:
Field 1 = Oracle user name
Field 2 = Oracle user password (select Yes for the Mask option)
Field 3 = Oracle database name
If you need to access the SAP application, for SAP credentials you might enter the following:
Field 1 = SAP user name
Field 2 = SAP password (select Yes for the Mask option)
Field 3 = SAP system number
Field 4 = SAP client number
Field 5 = language
     7.     Click OK.
Step 5: Provide Account Information for an Application Definition
After you have created the application definition, for group application definition you have to specify the logon account credentials. For individual application definitions, you can specify credentials for the users or, alternatively, the users may enter their credentials in the logon form on the first access.
To specify the logon account information for the application definition, do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Enterprise Application Definition Settings section, click Manage account information for enterprise application definitions.
     3.     On the Manage Account Information for an Enterprise Application Definition page, in the Account Information section, do the following:
4.          1.     In the Enterprise Application Definition list, select the name of the application definition. If you created the application definition to use an individual account, the User account name box is displayed on the page. If you created the application definition to use a group account, the Group account name box is displayed.
2.          2.     In the User account name or Group account name box, type the account name that will be mapped to the application credentials.
3.          3.     Click OK.
     4.     On the Provide application_definition_display_name Account Information page, in the Logon Information section, enter the credentials to be used for the logon to the enterprise application. The number, the order and the names of the fields displayed follow configuration in the Logon Account Information section of the application definition.
Step 6: Enable the Single Sign-On Service on the Front-End Web Servers
After you have configured the single sign-on settings on the job server, you need to enable the single sign-on service of the front-end Web servers. To enable the single sign-on service on each front-end Web server, follow the instructions given earlier in step 2, Enable the Single Sign-On Service on the Job Server.
Managing Single Sign-On
After you have configured the single sign-on for the first time, you are likely to need to perform administration tasks at a later stage, including the following:
     Creating and deleting the application definitions
     Managing account credentials mapped within the application definitions
     Regenerating, backing up, and restoring the encryption key
     Enabling auditing of the encryption key
     Disabling the SSOSrv service
In this section, we will discuss the single sign-on administration tasks. If you need to change your single sign-on configuration, make sure you consider the following:
     The single sign-on configuration and encryption key management tasks cannot be done remotely. To configure single sign-on or manage the encryption key, go to the computer running as the job server and specify the settings locally.
     If you change the job server to another server, you must reconfigure single sign-on. After changing the job server, you must delete the entire registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ssosrv\Config on the old job server.
     If you reconfigure single sign-on and you want to change the account that you specified for managing the single sign-on service (the single sign-on administrator account), the user who reconfigures the single sign-on and the single sign-on service account must be a member of both the current single sign-on administrator account that manages the service and the new account that you want to specify.
Editing an Application Definition
You can edit the display name, the e-mail contact, and the logon fields for an enterprise application definition. You cannot edit the application definition name or change the account type.
To edit an application definition, do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Configure the Single Sign-on component and manage enterprise application definitions for portals.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Application Settings section, click Manage settings for enterprise application definitions.
     3.     On the Manage Enterprise Application Definitions page, rest the pointer on the display name for the application definition, and then click the arrow that appears.
     4.     On the menu that appears, click Edit.
     5.     On the Edit Enterprise Application Definition page, in the Application and Contact Information section, you can edit the display name and the e-mail contact.
     6.     In the Display Name box, type a display name for this application definition. The display name is what the user sees.
     7.     In the E-mail Contact box, type an e-mail address for users to contact for this application.
     8.     In the Account Information section, select one or more fields to map to the required logon information for this application definition.
     9.     Type a display name for each field as a reminder of the required information. The display names for the fields will appear on the logon page for the application.
     10.     To ensure that sensitive information, such as a password, is not displayed when viewing account information, click Yes for Mask?
     11.     Click OK.
Deleting an Application Definition
When you delete an application definition, it is removed from the single sign-on database. In addition, all credentials associated with the application definition are removed. To delete an application definition, do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Configure the Single Sign-on component and manage enterprise application definitions for portals.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
2.          2.     On the Manage Settings for Single Sign-On for server_name page, in the Application Settings section, click Manage settings for enterprise application definitions.
3.          3.     On the Manage Enterprise Application Definitions page, rest the pointer on the display name for the application definition, and then click the arrow that appears.
4.          4.     On the menu that appears, click Delete.
5.          5.     On the confirmation message box, click OK.
Managing Account Information for an Application Definition
You can update or delete individual account information for a single application definition, or you can remove an account from all application definitions.
For group application definitions, you can update the account information, but you cannot remove the Windows account from a group application definition because there is a one-to-one correspondence between a group application definition and the account. If necessary, you can delete the group application definition.
To manage account information for an application definition, do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Enterprise Application Definition Settings section, click Manage account information for enterprise application definitions.
     3.     On the Manage Account Information for an Enterprise Application Definition page, in the Account Information section, do the following:
4.          1.     In the Enterprise Application Definition list, select the name of the application definition.
2.          2.     If you created the application definition to use an individual account, the User account name box appears. If you created the application definition to use a group account, the Group account name box appears. In the User account name or Group account name box, type the account name to modify.
     4.     In the Enterprise Application Definition section, you can perform one of the three operations: update the account information for the application corresponding to this application definition, delete the stored credentials for this account for this application, and delete the stored credentials for this account from all application definitions.
   For individual application definitions, all three options are available. For group application definitions only the update option is available; both delete options are grayed out.
To update the account information for this application, do the following:
     1.     Click Update account information.
     2.     Click OK.
     3.     On the Provide application_definition_display_name Account Information page, in the Logon Information section, enter the credentials to be used for the logon to the enterprise application. The number, the order, and the names of the fields displayed follow configuration in the Logon Account Information section of the application definition.
     4.     Click OK.
To delete the stored credentials for this user account from this application definition, do the following:
5.          1.     Click Delete stored credentials for this account from this enterprise application definition.
2.          2.     Click OK.
3.          3.     To delete the user credentials, click OK on the confirmation message box.
To remove this user account credentials from all application definitions, do the following:
4.          1.     Click Delete stored credentials for this account from all enterprise application definitions.
2.          2.     Click OK.
3.          3.     To delete the user credentials from all application definitions, click OK on the confirmation message box.
Creating the Encryption Key
The encryption key is used as part of the encryption process for credentials used with single sign-on. The key helps to decrypt encrypted credentials stored in the single sign-on database. The first time you configure single sign-on and enterprise application definitions on the Manage Server Settings for Single Sign-On page, the encryption key is created automatically. You can regenerate the key if the previous credentials are compromised or if you have a policy to change the key after a certain number of days.
When you create an encryption key, you can choose to re-encrypt the existing credentials with the new key. When you re-encrypt the SSOSrv service credential store, events are logged in the Microsoft Windows Server 2003 application event log. Once re-encryption is initiated, you can monitor the application event log to verify that the credential store has been re-encrypted. Event ID 1032 is recorded in the application event log when re-encryption is started. Event ID 1033 is recorded in the application event log when re-encryption has ended. If there are any failures during re-encryption, an event is recorded in the log.
If the job server is restarted or SSOSrv is stopped on the job server during the re-encryption process, you should look in the event log for errors. If the event log reports an error, you must restart the re-encryption process from the Manage Encryption Key page.
   If the re-encryption process is preempted in any way, it will have to be re-run. If the re-encryption process is preempted, it reverts back to its original state
The re-encryption process is a long-running operation. It is recommended that you change or restore the encryption key during non-peak periods.
During the re-encryption process, Write operations such as updating credentials and changing application definitions are not allowed. Read operations such as retrieving credentials continue to work as normal.
   To re-encrypt the existing credentials, the single sign-on service account must be a member of the Server Administrators server role on the SQL Server instance where the single sign-on database is located. For other requirements for single sign-on service account, refer to the section Single Sign-On Service Account earlier in this chapter.
You cannot create the encryption key remotely. To re-generate the encryption key, go to the computer running as the job server, log on as the single sign-on administrator account, and do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Server Settings section, click Manage encryption key.
     3.     On the Manage Encryption Key page, in the Encryption Key Creation section, click Create Encryption Key.
     4.     On the Create Encryption Key page, to re-encrypt the credentials for the single sign-on database, select the Re-encrypt all credentials by using the new encryption key check box, and then click OK.
   If you do not re-encrypt the existing credentials with the new encryption key, users must retype their credentials for individual application definitions, and administrators for group application definitions must retype group credentials.
Backing Up the Encryption Key
After creating the encryption key, you should back it up. You must back up the key to a 3.5-inch floppy disk. You should lock up the backup disk for the encryption key in a safe place.
   Because the encryption key is the key that decrypts the encrypted credentials stored in the single sign-on database, the backup copy of the key should not be stored with the backup copy of the database. If a user obtains a copy of both the database and the key, the credentials stored in the database could be compromised.
You cannot back up the encryption key remotely. To back up the encryption key, go to the computer running as the job server, log on as the single sign-on administrator account, and do the following:
     1.     On the SharePoint Portal Server Central Administration for server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for server_name page, in the Server Settings section, click Manage encryption key.
     3.     Insert a 3.5-inch disk into a disk drive on the computer running as the job server.
     4.     On the Manage Encryption Key page, in the Encryption Key Backup section, in the Drive list, click the letter of the disk drive, and then click Back Up to back up the encryption key.
     5.     In the completion message box that appears, click OK.
     6.     Remove the 3.5-inch disk from the disk drive.
Restoring the Encryption Key
You cannot restore the encryption key remotely. To restore the encryption key, go to the computer running as the job server, log on as the single sign-on administrator account, and do the following:
     1.     On the SharePoint Portal Server Central Administration for Server server_name page, in the Component Configuration section, click Manage settings for single sign-on.
Alternatively, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Single Sign-On Administration.
     2.     On the Manage Settings for Single Sign-On for Server server_name page, in the Server Settings section, click Manage encryption key.
     3.     Insert a 3.5-inch disk into a disk drive on the computer running as the job server.
     4.     On the Manage Encryption Key page, in the Encryption Key Restore section, in the Drive list, click the letter of the disk drive, and then click Restore to restore the encryption key.
     5.     Click OK.
When the restore completes, the Manage Settings for Single Sign-On for Server server_name page appears.
     6.     Remove the 3.5-inch disk from the disk drive.
   Restoring the encryption key and re-encrypting the single sign-on credentials store with the restored key is a long-running process. It is recommended that you restore the encryption key during non-peak periods.
Enabling Auditing for the Encryption Key
You should enable auditing for the encryption key. Then, if the key is read or written to, there will be an audit trail in the security log in Microsoft Windows Server 2003 Event Viewer.
To enable auditing for the encryption key, you need to modify the registry using regedit and then enable auditing using Group Policy Object Editor.
To modify the registry, do the following:
1.     On the taskbar, click Start, and then click Run.
2.     Type regedit and then click OK.
3.     In Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ssosrv\Config.
4.     Right-click Config, and then click Permissions.
5.     In the Permissions for Config dialog box, click Advanced.
6.     In the Advanced Security Settings for Config dialog box, click the Auditing tab, and then click Add.
7.     In the Select User, Computer, or Group dialog box, in the Enter the object name to select box, type everyone.
8.     Click OK.
9.     In the Auditing Entry for Config dialog box, in the Failed column, select the Full Control check box, and then click OK.
10.     Click OK, and then click OK again to close all dialog boxes.
11.     Close Registry Editor.
To enable auditing, do the following:
     1.     On the taskbar, click Start, and then click Run.
     2.     Type mmc and then click OK.
     3.     In the console, on the File menu, click Add/Remove Snap-in.
     4.     In the Add/Remove Snap-in dialog box, on the Standalone tab, click Add.
     5.     In the Add Standalone Snap-in dialog box, in the Available Standalone Snap-ins list, click Group Policy Object Editor, and then click Add.
     6.     In the Select Group Policy Object dialog box, ensure that Local Computer appears in the Group Policy Object box, and then click Finish.
     7.     In the Add Standalone Snap-in dialog box, click Close.
     8.     In the Add/Remove Snap-in dialog box, click OK.
     9.     Expand the following nodes:
     Local Computer Policy
     Computer Configuration
     Windows Settings
     Security Settings
     Local Policies
     Audit Policy
     10.     In the details pane, double-click Audit object access.
     11.     In the Audit object access Properties dialog box, select the Failure check box, and then click OK.
You can verify that auditing is working by doing the following:
12.          1.     Log off.
2.          2.     Log on as a user who should not have access to the registry key.
3.          3.     Try to read the registry key.
4.          4.     Look in the security log in Windows Server 2003 Event Viewer for audit entries.
Disabling the Single Sign-On Service
To disable the single sign-on service on the server farm, you must disable it on each front-end Web server, on the job server, and on any server running the single sign-on service.
If you want to delete all credentials associated with application definitions, you must delete each enterprise application definition.
To disable the single sign-on service, do the following on each front-end Web server, job server, and any server running the single sign-on service:
     1.     On the taskbar, click Start, point to Administrative Tools, and then click Services.
     2.     On the Services management console, double-click Microsoft Single Sign-on Service.
     3.     On the General tab, in the Startup type list, click Manual.
     4.     In the Service status section, click Stop.
     5.     Click OK.
Creating a Web Part That Uses Single Sign-On
After you have configured the single sign-on and created the application definitions, you need to develop a Web Part that implements the single sign-on functionality and retrieves information from the corresponding back-end application programmatically.
SharePoint Portal Server 2003 provides a programming interface for developers to use and extend the single sign-on feature. There are two namespaces provided solely for interaction with the single sign-on functionality, as well as one class in a more generic Microsoft.SharePoint.Portal namespace, as follows:
          The Microsoft.SharePoint.Portal.SingleSignOn namespace contains core classes that allow you to work with account credentials and application definitions in the single sign-on credentials store. These core classes and their functionality are listed in Table 26-1. The required assembly is Microsoft.SharePoint.Portal.SingleSignon, located in Microsoft.SharePoint.Portal.SingleSignon.dll.
          The Microsoft.SharePoint.Portal.SingleSignOn.Security namespace contains two classes that control the ability to access Single Sign-On resources programmatically from the code. These two classes and their functionality are listed in Table 26-2. The required assembly is Microsoft.SharePoint.Portal.SingleSignOn.Security, located in Microsoft.SharePoint.Portal.SingleSignOn.Security.dll.
          The SingleSignonLocator class in the Microsoft.SharePoint.Portal namespace allows you to locate a URL for the logon form for the SSOSrv service. It has the GetCredentialEntryUrl(strAppName, [port]) method that returns the URL for the logon form for a given application definition. The method takes two parameters: strAppName, which is a name of an application that is configured in the corresponding application definition, and the optional port number for SSL. If you do not specify the port number, and SSL is not enabled on the server, the port number will default to port 80 (that is, the port value will be omitted from the URL). If the second parameter is absent and SSL is enabled on the server, the port number is assumed to be the standard SSL port 443. However, if you require the URL returned to be formatted for SSL on a particular port, you need to specify it. For example, you would pass the specified port when the system cannot detect which SSL port to use, such as when multiple SSL port mappings exist. The required assembly for this class is Microsoft.SharePoint.Portal, located in Microsoft.SharePoint.Portal.dll.
Table 26-1. Microsoft.SharePoint.Portal.SingleSignOn Namespace Core Classes
Class     Description
Application     Exposes functionality to add, get, and delete enterprise application definitions
Credentials     Exposes functionality to manage user and group credentials and access tokens
SSOReturnCodes     Contains all the return codes for SSOSrv service that the SingleSignonException class will throw
SingleSignonException     Instantiates an exception from the SSOSrv ser vice with a specific error code
Table 26-2. Microsoft.SharePoint.Portal.SingleSignOn Security Namespace Classes
Class     Description
SingleSignOnPermission      Allows security actions for SingleSignOnPer mission to be applied to code using declarative security.
SingleSignOnPermissionAt tribute     Represents a custom permission that controls the ability to access Microsoft SharePoint Products and Technologies resources to manage user and group credentials and access tokens.
For example, lets look into a code in the Web Part that retrieves the account credentials for a back-end enterprise application from the single sign-on credentials database. The corresponding application definition is configured to use individual accounts. The code checks whether a requesting users credentials have already been stored in the single sign-on credential database. If not, the user is redirected to the Single Sign-On logon form to enter the required credentials for accessing the back-end application.
The code should implement the following sequence:
     1.     Call the GetCredentials method of the Credentials class. Specify the application name for which the credentials need to be retrieved from the single sign-on database.
     2.     If the SSOSrv service cannot find credentials for the user for the enterprise application specified, the GetCredentials method throws a SingleSignonException. If the LastErrorCode property of the SingleSignonException is SSO_E_CREDS_NOT_FOUND, call the GetCredentialEntryUrl(String) methodor the GetCredentialEntryUrl(String, Int) methodof the SingleSignonLocator class to build the URL to the single sign-on logon form.
     3.     After the URL for the logon form has been retrieved, redirect the browser to this URL. The logon form is created by the SSOSrv service. It prompts the user to enter credentials for the enterprise application in a number of fields. The order, the number and the display names for these fields are configured within the application definition under Logon Account Information. For example, if the enterprise application uses user name and password for authentication, two fields will be present in the logon form. For SAP, you may need five fields. After the SSOSrv service saves the credentials, the form redirects control back to the original Web Part.
The code in your Web Part will be similar to the following example that shows how to redirect the user to the logon form to save credentials for an enterprise application called SampleApp:
protected override void RenderWebPart(HtmlTextWriter writer) //RenderWebPart
string[] rgGetCredentialData = null;
try
//Try to get the credentials for this application.
//Before running this code, make sure that an individual
//application definition for application called "SampleApp"
//has been added.
    Credentials.GetCredentials(1,"SampleAPP", ref rgGetCredentialData);
catch (SingleSignonException ssoe)
//This exception will be thrown if this user does not have
//credentials for the "SampleApp" application.
    if(SSOReturnCodes.SSO_E_CREDS_NOT_FOUND == ssoe.LastErrorCode)
      //Send the user to the single sign-on logon form.
      //The logon form will:
      //- Prompt the user for credentials for this application
      //- Save credentials for this user for this application
      //- Then redirect the user back to this Web Part
        string strSSOLogonFormUrl = SingleSignonLocator.GetCredentialEntryUrl
          ("MyIndividualApplicationID");
        writer.Write("<a href=" + strSSOLogonFormUrl +">Click here to save your
         credentials for the Enterprise Application.</a>");
        writer.WriteLine();
After the user credentials for the enterprise application have been stored in the single sign-on database, the custom code in the Web Part should retrieve the credentials using GetCredentials method, then submit them to the enterprise application in a manner that is relevant to this application, then retrieve the necessary data from this application, and then finally render the data in the Web Part. Referring back to Figure 26-1 that shows eight steps described in the section How Single Sign-On Works, the preceding code corresponds to steps 1 through 5. In addition to this code, you have to implement steps 6 through 8.
Your code for interacting with the enterprise application such as submitting credentials and retrieving information will be different depending on the type of application you are accessing. You need to consider that in an enterprise environment, where a user interacts with many systems and applications, it is likely that the environment does not maintain the user context through multiple processes, products, and computers. This user context is crucial to provide single sign-on capabilities because it is necessary to verify who initiated the original request. To overcome this problem, SharePoint Portal Server provides ability to use a Single Sign-On (SSO) ticket (not a Kerberos ticket). An SSO ticket is an encrypted access token that can be used to get the credentials that correspond to the user who made the original request. Also, in the enterprise environment you might consider using Microsoft BizTalk Server as a transformation engine for the authentication requests, as well as requests for data, between your Web Part and a format that is understood by the enterprise application.
An example of such enterprise application integration (EAI) infrastructure is shown in Figure 26-2. In this scenario, a Web Part gets the information from a line of business (LOB) back-end application using BizTalk Server 2004. The LOB application requires authentication. In this example, we will assume that the enterprise application definition for the LOB application has already been created, and the user credentials have been stored in the SSO database.
The authentication process shown in Figure 26-2 consists of several steps, as follows:
     1.     The Web Part calls Microsoft.SharePoint.Portal.SingleSignon.Credentials.ReserveCredentialTicket() with the user. This method reserves a credential ticket for the user and then returns an encrypted access token (SSO ticket) to the calling Web Part.
     2.     The Web Part passes the SSO ticket to the BizTalk Server 2004 native SOAP adapter by calling a Web service that runs on BizTalk Server. The SSO ticket is passed within the header of the SOAP request. When the SOAP adapter receives a request containing an SSO ticket, the ticket is stored as the SSO Ticket property in the conte

Use single sign on for multiple portal domains

Is it possible for a user to sign on once to a domain, and then be able to access other domains. What I'm trying to do is have one user registration page/login page, but use different portal server domains to present different sites, while at the same time having a type of single sign on, once a user has entered his credentials. Thus my registration process will create a new ldap user in an external directory, and i can then just point all the different domains to that External Ldap directory.

I wouldn't recommend this because it would affect performance plus there are potential other issues like conflict that you would run into ..
Everytime a user logs into a new session is created for him and this means a user might have multiple sessions on the server. The cookie that is also set is dependent on per portal domain so it might not work ..
An alternative approach might be to have multiple roles and then customize the role for different views. You can modify the membership code in such a way that based on certain criteria you can assign him to a particular role, equivalent to your domain. However the problem could be if you want to provide delegated admin, currently the delegated admin is only at a domain level.

Single Sign On is not working when deploying a Wi-Fi profile from Configuration Manager 2012 R2

Hello,
Trying to deploy a wireless profile to a user collection everything works except for the single sign on.
The user will get the wireless profile and be able to connect successfully but when the user signs on again to the same device the Wi-Fi will not connect before the logon process starts.
So GPO processing and home drive mappings are not occurring. The Wi-Fi profile is configured for "Single Sign On - Perform immediately before user logon"
These same settings can be managed successfully by GPO. It would be really nice to be able to use ConfigMgr though!
Thank you.

Hi,
Please refer to the links below:
Single Sign-On Profile Sample
http://msdn.microsoft.com/en-us/library/windows/desktop/aa369849(v=vs.85).aspx
Wireless Single Sign-On
http://technet.microsoft.com/en-us/magazine/2007.11.cableguy.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Single sign-on using Oracle Identity Management

Hi All,
I am new to Oracle Identity Management. We are planning to implement Oracle Identity Management in our environment, which consists of :
* Microsoft Active Directory.
* Microsoft Exchange
* Oracle eBusiness Suite Release 12 running on RedHat Enterprise Linux 5.5
Is it possible to implement single sign-on using Oracle Identity Management. Once you integrate Microsoft Active Directory, Microsoft Exchange & Oracle eBS, a user should not be prompted to enter password to access Oralce Applications once he logins to his computer/Windows.
Thank you for your time.
Thanks

Hi,
You need to use different product eSSO for single sign on. to manage user credentials for applications from OIM then you need to implement Provisioning Gateway connector.
Once you have eSSO Logon manager running on users workstation, user will be prompted for credentials for first time then going forward it will not ask.
Regards,
Raghav.

Implementing Single Sign-On in J2SE Application

I am developing a application which is going to do some Single Sign-On authentication.
For those who do not know what Single Sign-On is: For user who have multiple usernames and password for different web site, Single Sign-On offers them a way to authenticate to these different site without the need to remember all those passwords. It takes over the authentication process, and authenticates to these web sites for the user. The usernames and passwords are stored in a database.
I am going to develop such a program in Java. This program is going to fetch the web site which contains the login form. Find out what to send to the web server. Send the username and password stored for that web site and in return if authentication goes through the web site will send the web page to the Java program which when receive it will open it in a web browser.
Does anyone have any idea how I can implement this Single Sign-On feature? I know there exist several applications for windows which offers such Single Sign-On and which works with Internet Explorer. So somehow I should be able to make such a feature for a Java application.

Thanks for the reply
Should I read the following from the document you sent in Section 4.5? I just wanna confirm..
4.5 Configuring Custom SSO Environments
For information about configuring Oracle Business Intelligence to participate in custom SSO environments (for example, setting up SSO using Active Directory or SiteMinder), see articles 1287479.1 and 1274953.1 on My Oracle Support at:
https://support.oracle.com

End-user license agreement doesn't appear

I have a MAC, i have used adobe for ever, when i updated it, i am unable to agree to the end user agreement. that screen never shows up. when I try to force it on a different screen, it says that i need to sign the end user agreement. on the down load, when it goes to the finish 3 of 3 screen, it goes to the other products you may want screen. HOW do you get to the end user agreement screen? PLEASE HELP.

With Reader closed, open your Applications folder, double click on the Reader icon, and accept the agreement.

How to enable end users to escalate requests outside of newScale - end user view of delivery plan

How do you communicate to end users in a large organization, the procedures for escalation a request that is late or urgent. The views of the delivery plan available to users don't give them muche detail about who is doing the work.
I'm curious how other people communicate the escalation procedures - per service - to the end users that submit them? for instance, our unix admin team is pretty swamped and not meeting their OLAs reliably. They want to provide a way for the Appdev/IT users to know how to escalate requests that are late and urgent/important.
When a user submits a unix admin service on a req, if the user knows where to look in myservices, they can see the delivery plan, but enough detail to know who is doing the work. (we submitted an enhancement request a while ago to provide an options for a "full disclosure" view of the delivery plan). Even if they have enough access to service manager to find the req number and see the service manager view of the delivery plan, they still only see the service team/queue name, which might not be enough info for them to make a call or send an email.
We are discussing a few options and was curious what others are doing:
1. Update the Service description to include a contact distribution list for the fulfillment team (for requests with simple plans) or the service owner team for complex delivery plans.
2. Create a custom email template to be sent at start of delivery plan. Ccurrently we have a generic email that covers most requests, but are thinking of creating emails that provides service-specific escalation information.
3. Create an intranet page with escalation information by service, and perhaps including this as a link off the myservice home page or the service description.
The scope of this question is more around infrastructure requests that are fulfilled by centralized groups, not how end users escalate phone or computer requests. Our service-desk generally not involved in support of infrastructure requests, although they woudl probably be the escalation point for end-user requests
-Brian
running 2009.sp2

create a CSI program (from ITIL) that will be empovered to fix the issues with Unix admins, ie hire more people.
Dont fix process issues with technology, fix the process itself

CUP 5.3 - Single Sign On fu00FCr end user request screen?

Similar Messages

Maybe you are looking for