Mail, Exchange, Acitve Directory and Single-Sign On Issues

I have a brand new MacBook Air with Mavericks. 10.9.3.
We are using a single sign on account setup for our machines. I enter my exchange log in details to access my account on my computer. It's labeled as a managed mobile account. When I open Mail, it takes forever to connect with the exchange server and download and sync new email. The activity monitor shows it constantly running. I send an email and it takes minutes until it actually sends. When I try to shut down mail I usually have to force quit it to close the app because it's doing some kind of syncing with the server.
I have all the same settings on a Mac Mini running 10.9.3 except I'm using a local user/admin sign-on. No issue there. So I think it's something with the single sign on on my Air. Any help would be appreciated!

Try a restart.
Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.
Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account
If the problem is still there, try booting into the Safe Mode using your normal account.  Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.
Safe Mode
Safe Mode - About
General information.
Isolating issues in Mac OS X
Step by Step to Fix Your Mac
You also have 90 day telephone support from Apple Support.
Apple Support Contact
Apple Support contact - Telephone

Similar Messages

  • 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 site–based 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 site–based 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 site–based 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, let’s consider two different scenarios—a 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 user’s 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 user’s 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 user’s 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 user’s 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, let’s 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 user’s 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) method—or the GetCredentialEntryUrl(String, Int) method—of 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

  • How to configure Exchange 2013 OWA with Single Sign On

    Hi All ,
    How to configure Exchange 2013 OWA with Single Sign On ?
    Thanks .

    Hi,
    From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
    Exchange 2013 OWA Single Sign on with Exchange 2010
    https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
    If that is not your case, please feel free to tell me.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Wireless Network Policy Single Sign On Issue with Windows 8.1 only

    I'll try to set this up as best I can. I have a laptop with a fresh Windows 8.1 install on it. It is on my domain, and I have a single GPO applied to it. In the GPO under Computer Configuration -> Windows Settings -> Security Settings ->
    Wireless Network Policies I have created a Windows Vista or later policy. In the policy I have configured single sign on.  I log into a local account on the laptop and plug it into a wired connection. I then run gpupdate on it. At that point I unplug
    the network cable, and log off. Now, from the login screen I click Other user, and it looks like the screenshot below.
    Notice that "Windows will try to connect to" is present. I can login using domain credentials, and single sign on works perfectly. Now if I reboot the machine, the "Windows will try to connect to" is gone and single sign
    on does not work. If I log in with a local account and log out. The "Windows will try to connect to" is present again. I can login normally using domain credentials, and single sign on works perfectly again.
    One other note: I installed a fresh copy of Windows 7 on the same model laptop, and put it in the same OU with that single GPO. Single sign on works perfectly with the Windows 7 machine every time. Including after reboots. Thank you, in advance,
    for any advice or comments. I will be happy to provide additional information if it is needed.

    I managed to get this to work properly in my environment. I realized that I needed to export the wireless profile from the Group Policy editor and import it on the client (by using Group Policy). I realized this while reading through this article:
    https://technet.microsoft.com/en-gb/magazine/2007.11.cableguy.aspx
    You can see the "Export..." button in the screenshot posted by keyserag above. Select the profile name, in the Group Policy editor Properties dialog, i.e. the item that keyserag has blurred in his screenshot, then click the "Export..."
    button. You will be prompted to save the XML file. 
    I use Computer Configuration > Preferences > Windows Settings > Files to copy the XML file to the clients:
    Destination: %WindowsDir%\WirelessProfileExportFileName.XML
    I then use Computer Configuration > Preferences > Control Panel Settings > Scheduled Tasks to run netsh and import the profile:
    Action: netsh wlan add profile filename="%WindowsDir%\WirelessProfileExportFileName.XML"
    The PCs using my policies are now ready to logon without any need for additional manual actions.
    I've left out some detail here, I assume everyone will do something a little different anyway. Let me know if you need more help with this.

  • Exchange Server Deployment Assistant - Single Sign On Question

    I'm running through the Exchange Server Deployment Assistant to help with a Hybrid deployment and for
    right now, I don't want to be bothered with SSO. In the Assistant, when I answer
    No to the Do you want all users to use their on-premises credentials when they log on to their Exchange Online mailbox? question when I get to the
    Before You Begin section it always shows my answer to that question as being
    Yes.
    Any ideas? Can I simply ignore the sections that relate to AD FS as I work through the steps?
    Thanks!

    Hi Adare,
    I have tested on Exchange Server Deployment Assistant with "Hybrid"->"Exchange 2010 based hybrid", and get the same result as yours.
    Information on "Do you want all users to use their on-premises credentials when they log on to their Exchange Online mailbox?" as below:
    Single sign-on allows users in both the on-premises organization and the Exchange Online organization to access resources and features across the two organizations without being prompted for additional user credentials. Single sign-on is configured for
    a hybrid deployment using identity federation and Active Directory synchronization. If you're planning to have on-premises users access Exchange Online accounts using the Outlook mail client or planning to implement Exchange Online Archiving,
    we strongly recommend selecting Yes for this question and deploying single sign-on in your on-premises organization.
    It seems that this is the reason why Yes has been selected.
    Thanks 
    Mavis Huang
    TechNet Community Support

  • RSWUWFML2 Settings and Single Sign On

    Good day all.
    We're using Lotus Notes as our e-mail client and we're able to send work item to Lotus Notes.
    1.Unfortunately everytime user execute attachment 'Execute Work Item.SAP', system prompt 'Not all data for SAP GUI shortcut is available:...'
    We already created a shortcut in user SAPLogon. I guess some mistake in SAP Gui Parameters and Command.
    What should I type in this SAP GUI Paramaters and Command?
    2. When user execute the attachment, system always asking for user and password. Is it possible to go directly to SAP without type in the user id and password?
    3. After executing the attachment of work item, is it possible to close the SAP session/ go back to Lotus Notes?

    The question is a year old, so I don't know if it is still relevant, but in case it is:
    1 and 2: What single sign-on solution are you using? If you use sap shortcut (sapshcut.exe) I think I can help you if you are willing to modify RSWUWFML2.
    3: I don't think this is possible unless you can use batch input to execute transaction code "/NEX".

  • Using LDAP and Single Sign On

    Hello
    I have many applications that log into a single directory using LDAP. I want to be able to use single sign on in Portal to this applications. Because the portal users and the applications users are the same is there a way to pass this information from portal to the applications directly without asking it to the user?.
    Thanks for any help

    How do the applications currently authenticate?
    What you really want is to have all the applications participate in Single Sign-On.
    There are 3 ways to do it...
    1. make the application an SSO partner application
    2. configure the application as an SSO external application
    3. incorporate the application into a 3rd party SSO solution with Oracle Single Sign-On as a participating app.

  • NCO and Single Sign On

    Hello,
    Please could someone explain how I can get my windows application to connect via single sign on.  Currently the application gets the necessary connection string from the SAPLOGON.INI file (via the SAPLogonDestination) and attempts a connection after requesting client, username, password and language.  Someone would like to use this application in their work environment (single sign on via Microsoft NTLM) and I wanted to know what needs to be done to implement this.
    Thanks,
    Charles

    There is quite a bit of information available in the NCo 2.x documentation (available in the VS online help): There is a whole chapter about SSO.
    Here are the steps in short:
    - You need a so-called GSS-provider that is install on both sides, client and SAP-Server.
    - For Windows the easiest solution is to use GSSNTLM or GSSKERB5 (for NTLM or Active Directory based SSO).
    - You need to configure the the provider on server side with some profile paramters and at the client side with some environment variables. OSS note 595341 contains the W2K-GSS-Provider as an MSI-Package that automatically sets the variables on client side.
    - Make sure that SSO works with SAPGUI.
    - Now you can use SSO also from NCo, by removing the password from the connection string and adding SSOPartnerName.

  • Authentication and Single Sign-On

    Does the Ironport support LDAP authentication with Single Sign-On. Or, is it only supported on NTLM? Can you setup multiple authentication realms to the same AD server, but call different AD groups? What I am trying to accomplish is to have single sign-on working and also have users places in certain access policies according to which AD group they are in. For instance, the marketing group would be placed into on access policy while HR would be place in another.

    Hello,
    Single Sign on is done on NTLM.
    If you go to your GUI? Top Right Hand side > Support and Help Dropdown >  Select On Line Help > Then search for working with authentication realms
    You will see as follows :
    An authentication realm is a set of  authentication servers (or a single server) supporting a single  authentication protocol with a particular configuration.
    You can perform any of the following tasks  when configuring authentication:
    Include up to three authentication  servers in a realm.
    Create zero or more LDAP  realms.
    Create zero or one NTLM  realm.
    Include an authentication server in  multiple realms.
    Include one or more realms in an  authentication sequence.
    Include realms of different  protocols in a single authentication  sequence.
    Assign a realm or a sequence to an  Access Policy group.
    You can do what you are trying to do with NTLM.
    I hope this answers your query.
    Regards,
    Eric

  • What is Exchange Virtual directory and its role?

    Hello there,
    I am new to Exchange and I started reading about Exchange Virtual directories. I am struggling to understand the concept behind Virtual directories in Exchange and what is the role of this component. Can someone please shed some light and better yet supplemental
    information to help me understand the concepts behind it? Let me know please. I am looking forward to any reply that would help.
    Regards,
    Lotusmail1
    Franz Garcia

    Hi,
    Thank you for your question.
    Exchange virtual directory is a directory which store some necessary URL to point to correspondent web page, those URL can provide service for user by Exchange server. it include the following component:
    On Exchange CAS server:
    Autodiscover: An important function of the Autodiscover service is to provide access to features for clients that are connected to your messaging environment. These features include the web-based offline address book (OAB), the Availability service, and
    Unified Messaging (UM). The Autodiscover service must be deployed and configured correctly for clients to automatically connect to features.
    ECP: The Exchange Control Panel is a Web application that runs on a Client Access Server providing services for the Exchange organization. This Exchange Control Panel is installed automatically when you install a Client Access server. To manage Exchange
    from just about anywhere, you simply need to enter the URL path for the application in your browser’s Address field. You can then access the Exchange Control Panel. By default, the Exchange Control Panel URL is
    https://yourserver.yourdomain.com/ecp.
    EWS: Exchange Web Services virtual directories support the calendar sharing and other functionality offered by Exchange Web Services. The Exchange Web services included in Exchange provide an XML messaging interface that enables you to manage Exchange store
    items and access Exchange server functionality from client applications.
    Microsoft-Server-ActiveSync: Exchange ActiveSync is a client protocol that lets you synchronize a mobile device with your Exchange mailbox.
    OAB: An offline address book (OAB) is a copy of an address list collection that’s been downloaded so a Microsoft Outlook user can access the address book while disconnected from the server. Microsoft Exchange generates the new OAB files and then compresses
    the files and places them on a local share. You can decide which address lists are made available to users who work offline, and you can also configure the method by which the address books are distributed.
    OWA: By default, when you install Microsoft Exchange 2013, you enable Outlook Web App. Microsoft Outlook Web App lets users access their Exchange mailbox from almost any Web browser.The Client Access server role provides proxy and redirection services for
    Outlook Web App.
    PowerShell: The Exchange Management Shell, built on Windows PowerShell technology, provides a powerful command-line interface for Microsoft Exchange Server 2013 that enables automation of administrative tasks. With the Shell, you can manage every aspect
    of Exchange. You can enable new email accounts, create Send and Receive connectors, configure database properties, manage distribution groups, and more. The Shell can perform every task that can be performed by the Exchange Administration Center (EAC) plus
    things that can't be done in the EAC. In fact, when you do something in the EAC, it's the Shell that's doing the work behind the scenes
    On Exchange mailbox server:
    PowerShell: this is the same with front CAS server.
    We could refer to the following link:
    https://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
    Jim Xu
    TechNet Community Support

  • Application Express and Single Sign on

    Has anyone got Application Express/HTMLDB to interface with a Single Sign on login screen, which is an external app, verify the user and password and proceed to the HTMLDB app?
    Any suggestions on session management?
    Thanks.

    Scott,
    I tried to search the same topic but unable to find any relevant thread. My requirement is also same. I want to implement single sign on on my htmldb application with an external system which maintains the user credentials and authenticate it.
    Could you please refer to any thread which discussed on the same topic?
    Thanks in advance,
    AM

  • R3 systen connection error and Single sign on probelm in QA BW system

    Dear all
    Last two week back we have migrated the QA BW system to HA environment by using the system copy method (backup/restore method), after that we are facing two issues.
    1.     In RSA1 go to Source system select the R3 system, then right click and then select the check after that we are getting below error message.
    BI unknown in source system
    BI IDoc type ZSQB007 is not the same as source system IDoc type
    The following errors occurred in the source system
    Incorrect IDoc type ZSPA014 in the ALE definition of the source system
    2.     We have connected our QA portal to BW system by using the single sign on for that we have to reload the single sign on certified both place ( Bw and EP side ) ?
    Kindly guide us
    Regards
    Sriram

    Hi bhuban
    Thanks for you reply
    In My case we have do the system copy from Qa standalone to High available Cluster environment (both Hardware are different), in that I am not go to change the logical system and all RF C's. It will remain same because of in our Z development they are hot code the system Name. From source system I can able to log in the BW system in other way its give error message.
    Kindly support us
    Regards
    Sriram

  • Index_service user and single sign-on

    Hello everyone
    We're using the DMS Business Package for KM in our EP6 SP16 Patch 2 portal.  All is working well, and now we'd like to use TREX to index the repository in order to search for documents.
    The problem is... we use the SAPLOGONTICKET to single sign-on people to the DMS system, instead of user mapping.  Due to this, assigning user mapping for the index_service user isn't working, and index_service isn't being allowed into the DMS repository in order to index the documents.
    Do we have to create a user called index_service on the R/3 side, and assign it read permission to everything in order to use TREX to create the index it needs?  Or is there a workaround for this on the Portal side?
    Thanks in advance,
    Fallon

    Hi,
    the best thing would be the mapping, I thought it would work either the SSO was activated or not. I thought that once the system can't match the user with SSO it would try with the mapped user.
    The problem if I am not wrong is that the index_service user can't be created in R/3 side, the name is too long. I guess you'll have to find another workaround.
    Gregori Coll Ingles.

  • OD, Kerberos, SPNEGO and Single Sign-On

    I have been asked to identify ways to improve a company intranet, the entire network is Mac OS X for both clients and servers. The first thing I though of was using Kerberos for Single Sign-on functionality. Is anyone familiar with any issues surrounding setting this up in an all OS X environment. The Intranet hosts a number of web applications that would need to be converted to use Kerberos authentication and I just wanted to know if anyone is aware of any issues with the Apache mod_spnego or Safari 2.x's support for SPNEGO that could make things difficult. Also, I'm coming up blank for all my searches for any implementation instructions that might be out there so if anyone knows of any implementation descriptions that could be really helpful.
    Thanks,
    James

    Hi,
    the best thing would be the mapping, I thought it would work either the SSO was activated or not. I thought that once the system can't match the user with SSO it would try with the mapped user.
    The problem if I am not wrong is that the index_service user can't be created in R/3 side, the name is too long. I guess you'll have to find another workaround.
    Gregori Coll Ingles.

  • Dialog work process and single-sign on

    Hi,
    I have read that we should have atleast 2 dialog work processes configured.
    can anyone tell me the reason why?
    what is the concept behind single sign-on?
    much appreciate ur help.
    regards,
    swaroop.

    Hi Swaroop,
    I have never heard of something like that before...
    You can read more about single sign on here,
    https://www.sdn.sap.com/irj/sdn/itpractices?rid=/webcontent/uuid/01c62876-0a01-0010-f5a5-d39e7651b9fd [original link is broken]
    and here,
    http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/frameset.htm
    Regards
    Juan
    Please reward with points if helpful

Maybe you are looking for

  • How can I copy songs from one iPod to another?

    I received a new iPod Classic (last generation) and I'm trying to transfer my songs from my old iPod Nano (also last generation). My iTunes library is also split up between my two parent's houses and I only have half the songs on my Nano in this comp

  • Is there a way to migrate data from one user account to another simply?

    Recently one of our employees has left the company. This user had pertinent images saved to their profile and we are needing to migrate those images to a new profile (Kiosk) so users can access the needed files. In InDesign I'm told it pulls file pat

  • Importing from photo booth, problems with length and sound

    I have a 15 min (277 MB) video clip from photo booth that I would like to post to youtube. I can't get it to work and have been wrestling with a few different programs: When opening the clip in Quicktime, there is no sound. I can open with VLC media

  • How can I get my metronome click to work with 12/8 meter in Logic?

    I'm trying to get my KlopGeist click to 12/8 music. I can get it work with 4/4 and click on divisions set to 12th, but I cannot get truely 12/8. It's ok to recore, but the notation is different. Can anyone give me an answer? Thank you.

  • Why iPad change the name of my photos (file name) ?

    I use the iPad to save my photos directly from the camera when I walk on the road. If I copy the files into Aperture they appear with the name given to it by the camera. If sending the files to the Dropbox they come up with completely different names