OSB 10.3 and custom signing policy
Good morning.
I had several problems receiving signed messages from a customer. We have an active intermediary proxy, with a custom policy based on "Sign.xml" to require signing of message body.
But out customer is signing using a third-party solution, so our proxy can't validate his message. We are trying to create a custom policy without "bea" namespaces, that is:
<?xml version="1.0"?>
<wsp:Policy
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="firma"
>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
</wsp:Policy>This policy seems to be ok, but when we try to attach this as a "Custom policy" in the proxy, it is not in the list of custom policies.
Can't Oracle process non-propietary policy file?.
Thanks.
Please refer section "Creating and Using Custom WS-Policy Statements" at -
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/security/ws_policy.html
Regards,
Anuj
Similar Messages
-
Hi,
I made a 10.3 proxy service with a sign policy , added a service key provider and configured wls / wsdl.
I need to provide a xml signature in the osb tester else I get an exception.
When I use the proxy service tester in OSB and select the service provider. then it works perfectly. In the output window I get an request and response with wsse security.
Now when I use OWSM with xml signature with the same jks keystore and use the same alias and call this OSB proxy server with the xml signature generated by owsm, I got an wssecurity exception , could not validate signature using any of the supported token types.
maybe someone can help meHi,
I didn't solve it, soapUI is nice for testing but I needed to make this work for production.
I will wait for fmw 11g -
Osb 10gR3 - Active Intermediary proxy with custom WS-Policy files
I'm setting up an Active Intermediary proxy, and the Security option on the proxy to "Process WS-Security header" is only usable when Custom Policy Bindings are assigned to the proxy. But I don't want to use the default Oracle policies.
The "Select WS-Policy" popup within OSB only shows entries under the Predefined Policy tab. Yet I have custom WS-Policy files which have been imported into OSB.
So what's the trick?Hi,
Below are the steps followed
- OSB Proxy service has 'oracle/wss_username_token_service_policy' attached to it.
- Iam invoking this from BPEL. BPEL process has 'oracle/wss_username_token_client_policy' attached.
- I can invoke the osb proxy from bpel by passing credentials - No Issues.
Now I need to put some authorization restriction to the proxy service, so only specific users can access that.
-I used Role=Admin as a policy condition restriction under security in Proxy service.
-Then I went to proxy test console and I added the 'oracle/wss_username_token_client_policy' credentials and weblogic/xxxxx at Transport section and I was able to invoke the process. Here weblogic has a Admin Role.
-I cannot invoke the same proxy service from BPEL in Jdeveloper now.
All Iam trying to do is to protect my proxy by authrorization policy.
Thanks
Jagan. -
Dear Forum
I was using Adobe version XI and the signature feature disappeared from the menu. Now I downloaded Acrobat Reader DC. Using the menu and instructions I created a signature ID and customized the signature; however, when I go to sign a document it only shows the name layout or graphic image? How do I go back to using the certificate that I created?
Any help would be greatly appreciated.
Regards
CarlosFirefox works fine on Windows 2000 SP4 for me.
Any chance you have a dial-up connection that uses a web accelerator to speed the loading of content? -
Problems signing in to PSE/PRE Forum and Customer Service
Hello-I am presently running PSE/PRE8 on a win8 computer with 12GB memory and1TB HDD. I am searching for information on PSE/PRE12. However, I am having problems with my PW/ID. I understand that Photoshop.com has been eliminated and this is the source of my sign-in problem. I change my PW and the new PW works for a while and it becomes the incorrect PW or User ID. Also,I added a new email address to support email problems. I was sent an email to click a verify link but the link was not included and the email was a noreply. I cannot contact Customer Service because it is sending noreply emails. I was able to signin to the forum during my last visit but was told that I was not eligible to post messages not answer post. I need to be able to reach Customer Service but I preently do not have a method to contact it. Thanks.
Hello Jorma- Thanks for the response however,I cannot locate your response to my "Problems signing in to pse/pre forum and customer Service". I checked the Photoshop Elements forum but I was not able to locate the subject.
-
OSB to RestFul with Custom Header and Authentication
I am trying to add to OSB a RestFul service which requires authentication and custom http headers.
I am able to register the RestFul service as Business Service with following parameter
- Service Type: Messaging Service
- Request Message Type: None
- Response Message Type: Text
- Http Request Method: Get
- Authentication: Basic (Service Account)
When I test the Business Service in the Test Console, I passed in the custom http header and the content type and it did return back the JSON object I was expected.
However when I then try to create a Proxy against it with the following parameter, I had problem running it in the Test Console. Although I did pass in the http header it still complained that I didn't pass in the header. And as for Authentication, I was not even able to specify a service account like how I did in Business Service.
- Service Type: Messaging Service
- Request Message Type: None
- Response Message Type: Text
- Http Request Method: Get
Any ideas?
ThanksWhat type of service account are you using ? If it is static you need specify the username/password in the PS. Also you do not specify service account for a proxy service. What is the error in the logs.
If you have to pass the HTTP header use transport headers in your request, select request type as http and then set the content type and custom http header.
http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/modelingmessageflow.htm#i1125373 -
Custom Header and Custom policy
In one of my BPEL service I need to create Custom security policy which generated custom SOAP header.
To be clear when we use Usernametoken client security policy, Soap header with username and password elements gets generated for a request payload. In the same way I need to create a client policy which generates custom soap header while request is sent.
Can anyone suggest, how to do this.
SowmyaThanks Anuj all these says how to customize the existing policy
But my requirement is to create a custom header in SOA 11g
Example if we use WSSE UsernameToken Header, in SOAP request header we get as
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>username</wsse:Username>
<wsse:Password>password</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
In the same way I want to create a custom header
<soap envelope ch="namespace">
<soap:Header>
<ch::CustomHeader>
<ch:customelement1>Value1</ch:customelement1>
<ch:customelement2>Value1</ch:customelement2>
<ch:customelement3>Value1</ch:customelement3>
</ch:CustomHeader>
</soap:Header>
One of the options for this is to give an input header variable in the BPEL service invocation, but I do not want this way
Is there any other way to create it in em console since multiple services use this header
Thanks,
Sowmya
Edited by: 1004017 on May 10, 2013 8:20 AM -
Custom WS-Policy Files in Console Service Endpoint Polices List
hi
Not sure which WLS newsgroup for this so here goes.
I want to assign custom WS-Policy files to a web service via the console (i.e. post-deployment).
By default, the Service Endpoint Policies list only shows a small subset of default policy files within weblogic.jar and none of the Wssp1.2-* policy files. (i.e. only the proprietary WLS 9.0 WS-Policy files)
Is this correct behaviour? I want to experiment with policies based on the current WS Security Policy Standard without hard-coding the names of files into the service.
Is there a way to make these other supplied WSSecurityPolicy 1.2 policies appear in the list?
Thanks
Jim NicolsonHi,
Below are the steps followed
- OSB Proxy service has 'oracle/wss_username_token_service_policy' attached to it.
- Iam invoking this from BPEL. BPEL process has 'oracle/wss_username_token_client_policy' attached.
- I can invoke the osb proxy from bpel by passing credentials - No Issues.
Now I need to put some authorization restriction to the proxy service, so only specific users can access that.
-I used Role=Admin as a policy condition restriction under security in Proxy service.
-Then I went to proxy test console and I added the 'oracle/wss_username_token_client_policy' credentials and weblogic/xxxxx at Transport section and I was able to invoke the process. Here weblogic has a Admin Role.
-I cannot invoke the same proxy service from BPEL in Jdeveloper now.
All Iam trying to do is to protect my proxy by authrorization policy.
Thanks
Jagan. -
Hi Experts,
Could you please give info on Multiple and single sign on directory settings ?
Regards
Sarahi 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 -
My iPod touch wont let me buy anything, i've beem using this account for a couple of years and now it says that this is the first ime this id has been used on my device... it's not.... and to sign in and answer security questions. i cant remember the answers to the questions. How can i fix this without making a new account and losing all my stuff???
From a Kappy post
The Three Best Alternatives for Security Questions and Rescue Mail
1. Use Apple's Express Lane.
Go to https://expresslane.apple.com ; click 'See all products and services' at the
bottom of the page. In the next page click 'More Products and Services, then
'Apple ID'. In the next page select 'Other Apple ID Topics' then 'Forgotten Apple
ID security questions' and click 'Continue'. Please be patient waiting for the return
phone call. It will come in time depending on how heavily the servers are being hit.
2. Call Apple Support in your country: Customer Service: Contact Apple support.
3. Rescue email address and how to reset Apple ID security questions.
A substitute for using the security questions is to use 2-step verification:
Two-step verification FAQ Get answers to frequently asked questions about two-step verification for Apple ID. -
My experience in Toshibas product and customer services
Just a warning to people who may be considering purchasing a Qosmio based on my own experiences and the research I have done in the last week.
Toshibas customer service is simply not what it once was and there are 100s of reports of Qosmios of all generations suffering extreme issues just outside of warranty periods.
Ref: Toshiba Qosmio X500-149, Support call reference ********
I am writing to express my frustration, anger and disappointment in Toshibas product and customer services.
I am a Freelance Community Manager, Video Game and hardware reviewer in the video games industry presently looking after 2 communities for 2 employers totalling over 2.5m users, I travel to a lot of trade shows, expos and community meet and greets where I require a laptop suitable of showing the employers products which are usually AAA video games or editing video on the fly for publication to social networking sites.
In January of 2011 my 4 year old Alienware hit that point where it really needed replaced, I opted for a Toshiba Qosmio over the Asus G73 as there was a 300 price difference for near identical spec.
I managed to source a X500-149 at PCWorld the companies flagship model here in the UK paying 1499 for it on January 26th 2011 reduced from 1799.
For the 1st 13 month this laptop performed admirably aside a design issue of the fan guards that I raised on the 16th May 2011 with PCWorld where the heat expelled causes the rear guard plastics to become exceptionally brittle and crack. I evangelised the product to anyone who asked me what laptop and model it was that was running these AAA games in such great detail, something I certainly won't be doing in future.
In early March 2012 it then began randomly locking up requiring a hard reboot this would then suffer issues restarting, reporting Operating system could not be found this would usually point to a fault on the primary HD, disk checking software however reported no errors but this continued to happen which would lead me to suspect the motherboard.
Within a month of this problem starting the left laptop fan began making a horrible screeching noise and had a distinct wobble whenever high RPM's were required and the machine began to often go into thermal shut-down whilst performing my work duties and utilising graphics and higher than idle CPU.
I decided on the 23rd April 2012 that enough was enough and I was going to speak to Toshiba as for this to happen to a flagship laptop that was only just out of warranty was simply unacceptable.
23rd April called to report the issue and was basically told tough luck its out of warranty at this point I also updated my tel numbers with Toshiba as the info was outdated, after expressing my anger at this Toshiba agreed to offer me a extended warranty at a cost of 166.
I was fuming to say the least Toshibas flagship laptop breaks at 14 month old and I am expected to stump up more money. If I was not desperate as the machine is critical to my work I would have returned the machine to PCWorld under the sales of goods act and it not being fit for purpose.
As that course of action would likely lead to legal proceedings, engineer reports and even more delay than just dealing with Toshiba for a repair, against my better judgement I called back at 11am on 24th April paid the 166 and took Toshiba up on the warranty extension, order number ********** again having to provide correct tel numbers as where once again incorrect, immediately after I reported the faults.
Toshiba Support centre on fault reporting where great noting each issue in detail and raised a collection with UPS for the following day.
The evening of the 24th April whilst I was retrieving data from the laptop in preparation for factory resetting it the machine went into thermal shut-down with a very distinct smell of burning chemical/plastic coming from the rear vents.
It took me over 90 minutes to get the machine cool enough to actually reboot and get my data after this I shut it back down and boxed it up not be used again.
I thought the best course of action would be to report this as it was a fair step up from the previous overheating. Wednesday 25th April at around 9am I called Toshiba to report this and was advised this would have to be dealt with by a head office case manager, as the item had become hazardous thus the collection that would take the laptop to the service centre was cancelled.
At this stage the advisor took my contact numbers again and escalated the case to head office advising at that time that I would be called by HO within 24 hrs.
Thursday 26th April 15:31 Well past the 24 hr mark and no sign of a call so I called support again and spoke to a advisor called Jacob. Jacob advise that HO had indeed tried calling on 01670 ******* this number was my old number, this number was the number I had advised twice already was incorrect and had provided both a correct land-line and mobile number 3 times previously. To say I was annoyed was a understatement.
Jacob attempted to contact Chloe Sontag who was looking after my case but the line just rang out so Jacob advised that he had sent an email asking for Chloe to contact myself.
Friday came and still no contact by 15:00 so I called support who once again tried to patch me to Chloe who's number once again just rang out and again an email was sent asking to call me.
No call by 17:30 so I called tech support again and spoke to Ian asking for head offices number so I could call them direct, Ian provided the number yet advised that HO are now closed.
After expressing my frustration with this whole process and just how critical this machine is to my daily working life Ian promised to look into the case on Monday AM and try and expedite actually getting a phone call to at least start the process of having this laptop repaired.
To say I'm annoyed is really a understatement not only has this failure to receive a simple phone call at least delayed the repair by almost a week but it is costing me more and money daily when I spent a large amount on what I imagined would be a great laptop for 3-4 years and believed Toshiba actually had good customer service in the event something did happen.
My best guess is that Chloe is on holiday or is part time or such like as her phone just rings out and if that is the case then I would question why assign a case to her, if she isn't then I would want to know why after 2 additional mails advising that the customer is not happy and to contact them has there been no contact or are your case workers just so overworked with faulty products that they can't manage the workload ??
So far Toshibas inability to produce a product that last as long as you expect it would has cost me 2 days off work that I am having to make up this weekend thus cancelling prior commitments, 166 extended warranty 600 for a HP laptop that I had to go and purchase yesterday 27th April 2012 to actually perform my work on and who knows how much in phone calls by the time this matter will finally be resolved.
I was happy with Toshiba as a manufacturer and of course laptops can have issues however having now researched these issues far to many Qosmio X500 users report severe overheating just after the 12 month period or within it and many state that repair after repair has taken place but still to no avail, this on top of the cracking of the rear heat-sink guards has to be a design fault.
This letter will not arrive with you before I have hopefully had a phone call and my laptop has at least been collected for repair, If I have not had that phone call then I would expect another letter very shortly.
Why have I wrote this letter ? To express my disappointment with just how poor the durability of your flagship laptop is and also at just how poor your customer service are, 1500 is a lot of money in the PC purchasing scheme of things and to expect this quality of hardware and customer service is simply unacceptable.
I expect the repair to be expedited and if like some of the horror storys I have read online parts required will take 4 weeks + then I would expect a replacement laptop, not everyone uses these things for entertainment and whilst the HP I had to rush out and buy with money I didn't really have available can allow me to perform my core duties to the minimum it cannot allow me to perform my duties to my standards, my employers standards or my expectant communities standards.
This has been a really unfortunate series of events as I had been considering the X870 Ivy Bridge based on the Nvidia 670m Qosmio which would release soon and passing this X500 onto my partner but after these events and the fact that the HP laptop had to come out of the money saved for it then I can categorically state that will not be the case and I will instead opt for the Asus G55 or G75.
If this issue cannot be resolved to a satisfactory manner then I will have no option but to seek an independent engineers report as well as printing the myriad of similar reports of these issues on the internet and return the item to PCWorld.
In line with the sale of goods act 1979 a large electrical item has to be of satisfactory quality and fit for purpose for a period of 6 years whilst I wouldn't expect the full 6 years from a laptop I would expect at least 3-4 year especially considering that this is a near 2000 flagship model not a 200 budget model.
This is a action I really do not want to take as it will likely end in small claims court against PCWorld a company that on this occasion has done nothing wrong, I do not believe in punishing those who are not at fault so its a action I really wouldn't be happy with and I'm sure PCWorld one of if not the largest vendor of Toshiba products when you incorporate the rest of the DSG group wouldn't be too pleased with it either.
FrustratinglySo I received my laptop back today after having fans replaced and a good clean as well as the top cover replaced.
Opened the box and took the laptop out 1st thing I noticed was a screw rattling around inside, SIGH!!!!
Plugged the laptop in and attempted to boot it at this point it just cycle through finalisation of windows install and shutdown.
How could a laptop have been tested if it didn't even have windows installed ?
An hour later and I gave up unplugged it and lo and behold it actually booted when on battery only.
I then noticed that the SSD was full, oh wait no it wasn't the head office engineer in his infinite wisdom decided that partitioning a 64GB SSD to 2 drives barely even leaving enough for Windows on the C: and wait for it putting the HDD recovery on the second partition was a good course of action.
So a completely borked install and a screw floating around inside remind me how this particular engineer has a job ??
I spent the next 15 minutes just moving data around and creating and deleting partiitions to fix this mess up.
Grabbed HWMonitor to check temps and at an idle 50c on CPU and 36c on GPU they didn't look too bad,
Installed the Toshiba recommended Nvidia driver a driver I hasten to add that was released in 2010 as Toshiba have not updated the drivers for their flagship series laptop since then, They are happy to take your 1643 that the unit cost but then don't expect support for it.
Anyway that aside I then installed 1 of the games I work on and began to run the machine through our benchmark software wooooosh the temps shot up to 90c+ on both CPU and GPU and remained at this temp for the duration of the benchmark never quite triggering thermal shutdown, I then loaded into a warzone for further testing and sure enough half way through it the machine shut down due to thermal shutdown.
I then uninstalled the toshiba driver and tried a NVidia one sure enough as others have advised actual Nvidia drivers seem worse and thermal shutdown came so much earlier.
I have been to PCWorld today to begin proceedings of returning outside of warranty due to not being fit for purpose or of suitable quality. This is costing me a further 60 and at least 2 weeks more without a proper machine and will likely result in me getting about 1300 back from PCWorld.
So lets do the math on just what this will have cost me by the time its finished.
1634 Original purchase
166 Extended Warranty
600 Backup Laptop whilst this was away for a month
60 outside of warranty assessment
50 phone calls
I will probably receive 1300 back but then 1300 doenst buy me the spec I need for work so I will have to pull out another 300-400 for the required spec so lets add that to the original figures.
A Toshiba Qosmio, Toshibas flagship laptop will have cost me in total 2910 almost double its actual retail price.
I will NEVER buy a Toshiba product again and it will become my lifes mission to let everyone know just how terrible they are. -
GRC 10.1 custom security policy
On GRC Java system, I am not able to create custom security policy under UME->Configuration->Security Policy. I am able to create on all other systems except GRC and NWDI system I it related to support pack level or facility is not available on these releases
Thanks ShankarShailendra:
Might be because there is no Java stack. AC and PC now run on the ABAP stack and I think SAP recommends not using dual stack. The only Java stack in the GRC 10.0 landscape that I'm aware of is for ADS.
Thanks.
Matt -
I installed Adobe over a month ago when prompted that my trial was expired. We pay 19.99 a month, and when signed in it states our next payment is due Feb 5, 2015. Yesterday I got a prompt that my trial was expired and I couldn't open any pdf files anymore. I uninstalled and reinstalled and it worked all morning until just now, now it is prompting me that the trial is expired AGAIN. What do I do to fix this permanently??
You installed Adobe what? Assuming that perhaps you have a subscription for Acrobat XI Pro, I will move your post to the appropriate forum. You could also try to Contact Customer Care.
[topic moved to Acrobat.com Services forum] -
Hello,
I am storing a few Maps into Coherence - each map might have a few hundred entries. The problem i have at this point is with the eviction policies. If i set the high units on the front map of a near cache to be 100 - it never works. It sees 1 entry per map.
I created a custom eviction policy where it will remove items from my map when the size of the map reaches the high units of that particular near cache. The problem is that this item is no longer present in the front or back map.
Is there a way to create a custom eviction policy where i can evict entries out of the front map but not the back map?
ThanksWhen i put my maps into tangosol i just do:
NamedCache mCache = CacheFactory.getCache(cacheName);
mCache.put(cacheKey, deepCopy(cacheObj));
where cacheObject is a Map and i make a deep copy of that map for thread safety.
The map contains over 100 entries.
Here is my cache config file:
<cache-mapping>
<cache-name>CouponCache</cache-name>
<scheme-name>content-near-with-eviction</scheme-name>
</cache-mapping>
<!--
Near caching scheme for all Content Caches
-->
<near-scheme>
<scheme-name>content-near-with-eviction</scheme-name>
<front-scheme>
<local-scheme>
<scheme-ref>default-front-eviction</scheme-ref>
</local-scheme>
</front-scheme>
<back-scheme>
<distributed-scheme>
<backing-map-scheme>
<local-scheme>
<scheme-ref>default-back-eviction</scheme-ref>
</local-scheme>
</backing-map-scheme>
</distributed-scheme>
</back-scheme>
<!--
Specifies the strategy used keep the front-tier in-sync with the back-tier
-->
<invalidation-strategy>present</invalidation-strategy>
<!--
It specifies whether or not the cache services associated with this cache scheme should be automatically started at a cluster node.
-->
<autostart>true</autostart>
</near-scheme>
<!--
Default front cache eviction policy scheme.
-->
<local-scheme>
<scheme-name>default-front-eviction</scheme-name>
<!--
Least Frequently Used eviction policy chooses which
entries to evict based on how often they are being
accessed, evicting those that are accessed least
frequently first. (LFU)
Least Recently Used eviction policy chooses which
entries to evict based on how recently they were
last accessed, evicting those that were not accessed
the for the longest period first. (LRU)
Hybrid eviction policy chooses which entries
to evict based the combination (weighted score)
of how often and recently they were accessed,
evicting those that are accessed least frequently
and were not accessed for the longest period first. (HYBRID)
-->
<eviction-policy>
<class-scheme>
<class-name>com.att.uma.cache.eviction.MyEvictionPolicy</class-name>
</class-scheme>
</eviction-policy>
<eviction-policy>LRU</eviction-policy>
<!--
Used to limit the size of the cache.
Contains the maximum number of units
that can be placed in the cache before
pruning occurs.
-->
<high-units>100</high-units>
<expiry-delay>12h</expiry-delay>
</local-scheme>
I did not list all of the methods specified by the interface - as they are irrelevant to my issue.
Here is my eviction class:
public class MyEvictionPolicy extends AbstractMapListener implements EvictionPolicy
private final static Log log = LogFactory.getLog(DefaultUnitCalculator.class);
LocalCache m_cache = null;
public MyEvictionPolicy() {}
public void requestEviction(int cMaximum)
int cCurrent = m_cache.getHighUnits();
if(log.isDebugEnabled())
log.debug("* requestEviction: current:" + cCurrent + " to:" + cMaximum);
// eviction policy calculations
Iterator iter1 = m_cache.entrySet().iterator();
while(iter1.hasNext())
Entry entry = (Entry) iter1.next();
if (cCurrent > cMaximum)
if((entry.getValue() instanceof Map))
Map map = (Map) deepCopy(entry.getValue());
Iterator iter2 = ((Map) entry.getValue()).keySet().iterator();
while(iter2.hasNext())
if(cCurrent == map.size())
entry.setValue(map);
break;
String key = (String) iter2.next();
map.remove(key);
if(log.isDebugEnabled())
log.debug("* requestEviction: current:" + cCurrent + " to:" + cMaximum);
else
break;
} -
Hi xperts,
I want to create a custom password policy which shoud fulfil the following requirements.
1Allow additional alpha characters more other than A-Z and a-z. i.e the ones in Start button--->Programs>Accessories>System Tools>Character Map.
2.Expand the default special characters list
3 and we dont want email prefix(before @ to be used in the password).
Any Ideas if we can do this ?You can put your validation using Java Script on Create User Form.----this can fulfil my 3rd requirement.
or
you can create custom action class which will validate your password. Change the reference of OLD action class and replace it with yours.
I am a little new to sucg kind of customisations,can u just give me a little idea how exactly I can go about it..i.e which files to modify,which action class etc...
Also I want this password policy for a group of users and if I modify the action class will there be an effect on the policies associated with other resources?
Maybe you are looking for
-
Leopard install on ibook lost hard drive
I tried to install leopard on my macbook and installation completed. the system restarted and the installer came back. My hard drive is no longer recognized and I cannot get the install disk out. Any ideas on how to get my hard drive back?
-
No Synchronisation of Photos between iTunes 10.5 and iPhone 3GS after iOS 5
I made the Update to iTunes 10.5 on my Notebook with Windows XP and the Update to iOS 5 on my iPhone 3GS. I had a lot of Problems (the Backup had an Error, my outgoing Mails were all deleted in all Mail Accounts, the Synchronisation of Music and Apps
-
How do you set defaults in pages such as font and moving between cells in a table?
How do you set defaults in Pages such as font and moving between cells in a table?
-
Java Applet not loading in Safari
Hi folks. I just noticed a problem with Safari on my Macbook Pro. I'm trying to use Keepvid to download videos from Youtube but it no longer works. I load then link into Keepvid and then get the message "Java Applet Loading..". Except that it remains
-
OS: Windows Server 2008 R2 Enterprise Domain Level: 2008 Forest Level: 2000 We have Domain Administrators in our domain that reset passwords for user accounts, and the passwords the Administrators set them to are not being enforced follow our default