Collective PR's and single PR configuration in SPRO
PM Experts,
When the check button for "Collective PR" is checked in, i believe Std SAP settings is that a single PR will be generated for every work order irrespective of the number of Non-stock materials... I also think that If this check is not marked then for every new non stock item, system wil generate a new PR seperately.
Is my understanding true and right. please confirm.
Also my Query is
For External service procured and non stock material within same work order, does system genearte single PR or seperate PR for service and seperate for materials.
Can I have seperate PR's generated within the same work order for operation wise.like all components for opertaion line item 10 , one PR should be genrated. All non stock materials for operation line item 20, seperate PR should be generated. Is it possible?
Please clarrify.
Thnks in advance
Murad..
Well,
This is wat I found in DEV environment after testing..
If you mark the indicator for collective Req, only one PR is generated on the header level against one maint order,
All procurement related to Non-Stock materials, services will be procured with a single PR irrespective of the services or non-stock materials, irrespective of the operation line items etc....
If you dont set the indicator, then for every single item procured (non stock material) or service , system will generate a single PR for each single material or each single service hired...No of materials, will equal no of PR's...
Eg: If 3 non stock items mentioned in Componenets and 2 external services in operations tab page then a total of 3+2=5 individual PR's will be generated.
Thanks for everyones contribution and sharing their experience..
Murad Shaikh
Similar Messages
-
I am interested in purchasing Adobe's Creative Suite 6 Master Collection for Mac and Windows (Single User Educational License) FOR STUDENTS & EDUCATORS ONLY. I am purchasing this program for my son who attends George Washington High School: The College Academy in New York, New York. He is a sophomore and is interested in web design. I would like to know if he is eligible to use/activate the Creative Suite 6 Master Collection for Mac and Windows (Single User Educational License) FOR STUDENTS & EDUCATORS ONLY prior to my purchase.
Peru Bob makes a good point. I just assumed the OP understood what the System requirements | Adobe Creative Suite 6 were.
Nancy O. -
Single XML configuration file for all the SSIS packages(including parent and child packages)
Hi
I have some 16 ssis packages. source Db and destination Db for these packages are common. I am calling these child packages in a master package.
I want to use only one XML config file for this master.
How do i use same for all child packages?
and can i do it with parent package variable?I created a master package with a variable master, and in value i have entered the configuration file path.
Hi vjp dinu,
You should create variables in the parent package to pass values to variables in each child package rather than pass the file path of the XML Configurations file of the parent package.
As Visakh mentioned, you can achieve your goal by creating corresponding variables in the parent package for each child package, and enable Package Configurations for the parent package so that you can control the values through the XML Configurations file
for the variables of the parent package.
Supposing there is a variable FilePath in child package 1, a variable ServerName in child package 2, then, we need to create two variables pFilePath, pServerName in the parent package. After configuring the Parent package variable in each child package (e.g.
mapping pFilePath to FilePath, pServerName to ServerName), you can enable XML Configurations for the parent package, and expose the value property for both pFilePath and pServerName variables. In this way, you can modify the XML Configurations file of the
parent package and the specified values will passed to the child packages.
Reference:
http://microsoft-ssis.blogspot.com/2011/06/passing-variables-from-parent-package.html
Regards,
Mike Yin
TechNet Community Support -
I want to set up the Time Machine and I would love to use the Time
Capsule but since I already have a wireless router I need suggestions on
what other
external disks Apple could recommend to use with the Time Machine and
how to configure that disk.
A complication that I need to resolve is the fact that I am using Vmware
Fusion to be able to use Windows on my Mac. Now it seems that Time
Machine is not backing up my files
on that virtual Windows without additional configuration and my question
is whether you can advise me here or whether this is only a matter for
the Fusion virtual machine.If you want to use Time Capsule you can.. you simply bridge it and plug it into the existing router.. wireless can be either turned off or used to reinforce the existing wireless.. eg use 5ghz in the TC which is much faster than your 2.4ghz.
You can also use a NAS.. many brands available but the top brands are synology, qnap and netgear readynas series. These will all do Time Machine backups although how well always depends on Apple sticking to a standard. There are cheaper ones.. I bought a single disk zyxel which was rebadged and sold through my local supermarket. It actually works very well for TM at least on Snow Leopard. Major changes were made in Lion and again ML so do not instantly think it will work on later versions. I haven't tried it yet with those versions.
Any external drive can be plugged into the mac. Use the one with the fastest connection or cheapest price according to your budget. USB2 drives are cheap and plentiful. But no where near as fast as USB3 or FW800. So just pick whichever suits the ports on your Mac. Interesting Apple finally moved to USB3 on their latest computers.
TM should exclude the VM partition file.. it is useless backing it up from Mac OS side.. and will slow TM as it needs to backup that partition everyday for no purpose.. TM cannot see the files inside it to backup just the changes.
You need to backup windows from windows. Use MSbackup to external drive.. if you have pro or ultimate versions you can backup to network drive. But MSbackup is a dog.. at least until the latest version it cannot restore the partition without first loading windows. There are about a zillion backup software versions for windows.. look up reviews and buy one which works for you. I use a free one Macrium Reflect which does full disk backups and is easy to restore.. to do incremental backups though you have to pay for it. -
Assignment Between Structure and Single Field - CL_ABAP_CONTAINER_UTILITIES
Hi, Need some help on this as I'm not familiar with Java programming.
Basically in ABAP, we can assign a structure (with complex data type) into a field (please refer to link below).
Now we need to do similar thing in PI, since PI only support Java then we need to perform similar logic as in CL_ABAP_CONTAINER_UTILITIES =>FILL_CONTAINER_C, but in Java. Understand that there's no concept of structure in Java, in this case PI will receive multiple fields (with different data type) and need to combine them into one field.
I tried few Java command/method but it doesnt give me the same result as in the ABAP class. Appreciate your help if you know anything about this or some sample program that i can test. thanks!
SAP Help Reference for ABAP
[ABAP - Assignment Between Structure and Single Field|http://help.sap.com/saphelp_nw04/helpdata/en/79/c554d3b3dc11d5993800508b6b8b11/frameset.htm]Hello Rika,
In java we have collection framework instead...
As per your requirement I understood :
1. You will get a list of different type of objects as input.
2. You want to club it in one unit....right...
3. Once done.....I dont know what you will do with that.....I guess pass it somewhere.....
Now, You can use ArrayList in java to club all your objects in one unit....and send it to any function you want....
Arraylist list= new ArrayList();
list.add(new MachineGun());
list.add(new Gun());
But there be carefull when you extract data from List....as you need to type cast them accordingly....
Start trying it...and revert back if you face any problems.....
While extracting you will have to use something like :
if(list.get(0).getClass().getSimpleName().equals("MachineGun")){
//here you can safely cast in the right class
MachineGun mgun= (MachineGun )list.get(0); -
I have been unsuccessfully trying to extend the wifi of my Time 2T Capsule with an Airport Extreme 2nd Gen. It works for a while and then loses configuration. I have done everything possible, disconnected it, reset it but it keeps failing, what to do?
What model and firmware is the 2TB TC?
What firmware is the AE?
Does the AE get good signal from the TC in its current location?
Signal can only be extended that is received intact.
Is it extending on 5ghz? As I remember it a Gen2 AE is only single band, although you can choose either 2.4ghz or 5ghz.
I am fairly sure you are going to tell me your TC is AC model..
I would do a couple of things..
1. Fix the wireless name, make it short, no spaces and pure alphanumeric.
2. Fix the wireless channel for 2.4ghz so it is not going to jump around.
3. Get real results from the AE in its current location for signal strength.. this is really only possible on v5 utility. And that is a double pain with Mavericks because you cannot use it.
Apple have removed all the useful diagnostics from the airport utility. There is next to nothing left. So you need to use the computer and its diagnostics to find signal levels in the location.
http://support.apple.com/kb/HT5606 -
Class-Map and Policy-Map Configuration in CM Confusion
Hi,
I'm implementing a green field WAAS deployment for a customer. We currently have a Proof-of-Concept up and running.
I've got some questions regarding custom class-map and policy-map configuration in the CM. I'd like to nail-down the custom class-map and policy-map configuration (and understanding) in the PoC before cutting over the PoC branches to the production WAAS environment.
Assuming a typical WAAS Deployment using WCCP for off-path interception, branch to DC.
==> 61 in LAN (BRANCH ROUTER) <== 62 in WAN (WAN CLOUD) ==> 61 in WAN (DC ROUTER) <== 62 in LAN
We are using two distinct device groups, BRANCH and DATA CENTER.
If the customer has traffic that we need to classify in order to provide TFO only optimisation, should the single class-map include the traffic in both directions? Ie., (assume the SERVER is 10.1.1.1 TCP Port 443). Should the class-map be configured as:
Class-Map
Line 1: DST IP 10.1.1.1 DST Port 443
Line 2: SRC IP 10.1.1.1 SRC Port 443
Or in this case is only the DST line required? And in which Device Group should the custom policy be applied? Or should it be applied to both Device Groups? If it should be applied to both Device Groups, then would it make more sense to have the policy-map in the Branch DG configured to match the DST traffic, and on the Data Center DG have a different class-map match the SRC traffic?
My confusion is how to classify the traffic (SRC or DST or Both - Separate classes for each or different lines within the same class-map), and where to apply the appropriate policy (both Device Groups, just Branch, just DC) and why...
I tried to apply a custom policy and the impact in the PoC was that the TCP Summary report stopped reporting the individual traffic classes showed 'other traffic' only. Can anyone explain why this may have occurred?
I hope this makes sense.for instance like this:
policy-map police-in
class class-default
police rate 10 mpbs <optionally set burst>
policy-map shape-out-parent
class class-default
shape 10 mpbs <optional burst config>
service-policy shape-out-child
policy-map shape-out-child
class class-default
queue-limit 10 packets
int g 0/0/0/0
service-policy police-in in
service-policy shape-out-parent out
also have a look at CL 2013/2014 (orlando/sanfran) ID 2904 for more QOS details
and the support forum article of "asr9000 quality of service architecture"
xander -
What is load balancer in fms cluster and how to configure it and testing fms clustering
Hey guys,
I am new to fms and clustering the fms server in origin-edge mode.But i am confused actually what is load balancer and how to configure it .
After configuring , how to test and confirm that fms clustering is working.Is there any one can help me, plz....................
thanks in Advance........Flash Media Server does not come bundled with a load balancer. In theory, one deploys FMS in an edge/origin configuration like this
1 Origin ----> N Edges ------> Customer Traffic
The idea here is that N edges shoulder the load for most customers with a single origin coordinating resources like VOD content or script access. The issue that remains is "how do I spread customers over the N edges" and that's where load balancing comes in. Most customers use a prepackaged load balancing solution - as an Adobe staffer I can't recommend any of them over the other, but you should be able to get some recommendations here along with just googling for it. The short answer contained here though is, you're going to have to find one outside of FMS if that's needed for your setup.
Asa -
Geometry collections (gtype 4) and validation rules
Hi folks,
I am not finding anywhere any particular rules about how a geometry collection should validate. What is the best reference (even outside Oracle Spatial)?
Below is a collection geometry of a single point and three polygons (some of which overlap each other). When I remove the point and test the three polygons as a multipolygon I get back a 13351 error as expected. But when wrapped up in a collection I get back TRUE. Are there really any rules for collections? Or does anything go?
In this use case the collection is the source data but then I pull out the polygons further down the road and - whammo - invalid geometries.
I see the same results on both 10gR2 and 11gR2.
Thanks!
Paul
Collection Geometry of one point with three overlapping polygons - validates TRUE
SELECT
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(
SDO_GEOMETRY(
2004,
8265,
NULL,
SDO_ELEM_INFO_ARRAY(
1,
1,
1,
3,
1003,
1,
13,
1003,
1,
23,
1003,
1
SDO_ORDINATE_ARRAY(
-84.3508498737178,
45.9775103765449,
-84.3522809373541,
45.9723473947168,
-84.3522938852715,
45.9722956030474,
-84.3522161977673,
45.9722308634606,
-84.3522032498499,
45.9722697072127,
-84.3522809373541,
45.9723473947168,
-84.3522809373541,
45.9723473947168,
-84.3522938852715,
45.9722956030474,
-84.3522161977673,
45.9722308634606,
-84.3522032498499,
45.9722697072127,
-84.3522809373541,
45.9723473947168,
-84.3522809373541,
45.9723473947168,
-84.3522938852715,
45.9722956030474,
-84.3522161977673,
45.9722308634606,
-84.3522032498499,
45.9722697072127,
-84.3522809373541,
45.9723473947168
0.001
FROM
dualPoint removed making it 2007, now throws 13351 error
SELECT
SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(
SDO_GEOMETRY(
2007,
8265,
NULL,
SDO_ELEM_INFO_ARRAY(
1,
1003,
1,
11,
1003,
1,
21,
1003,
1
SDO_ORDINATE_ARRAY(
-84.3522809373541,
45.9723473947168,
-84.3522938852715,
45.9722956030474,
-84.3522161977673,
45.9722308634606,
-84.3522032498499,
45.9722697072127,
-84.3522809373541,
45.9723473947168,
-84.3522809373541,
45.9723473947168,
-84.3522938852715,
45.9722956030474,
-84.3522161977673,
45.9722308634606,
-84.3522032498499,
45.9722697072127,
-84.3522809373541,
45.9723473947168,
-84.3522809373541,
45.9723473947168,
-84.3522938852715,
45.9722956030474,
-84.3522161977673,
45.9722308634606,
-84.3522032498499,
45.9722697072127,
-84.3522809373541,
45.9723473947168
0.001
FROM
dualBaris,
I came across this on a different forum and was very, very surprised that it validates.
SELECT SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(
MDSYS.SDO_GEOMETRY(2005,4326,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,1,1,3,1,1,5,1,1),MDSYS.SDO_ORDINATE_ARRAY(18.5272949231966,43.9245558053237,18.527391754093,43.924240327095,18.5310243924313,43.9252225514267))
, 0.0001) IsThisOk
FROM DUAL
Based upon your comment then, validation sees the first element as correct ... what is the second and third element then? I assume points but this method of defining a multipoint is an undocumented feature :-) .... or did i miss something
This is what the fellow was actually looking for but he didn't pay much attention to the docs ....
MDSYS.SDO_GEOMETRY(2005,4326,null,MDSYS.SDO_ELEM_INFO_ARRAY(1,1,3),MDSYS.SDO_ORDINATE_ARRAY(18.5272949231966,43.9245558053237,18.527391754093,43.924240327095,18.5310243924313,43.9252225514267))
r,
dennis -
[Solved] Gwenview 5 lost icons and single click
Hi,
I don't use KDE but I do use Gwenview. Since upgrading to 5 Gwenview has lost some icons (outlined in red below), and I now have to double click on directories and images to open them instead of single click. Is it possible to fix these issues without installing a full KDE desktop?
Thanks, Jamie
Last edited by JamieKitson (2015-02-10 22:30:10)I get a much larger list in "kcmshell5 icons". I think because I installed "plasma-meta", and removed "kdebase-workspace".
kcmshell5 --list
The following modules are available:
kf5.kservice.sycoca: Trying to open ksycoca from "/home/johnm/.cache/ksycoca5"
autostart - Automatically Started Applications
bell - System Bell
bluedeviladapters - Configure Bluetooth adapters
bluedevildevices - Manage Bluetooth devices
bluedeviltransfer - Configure Bluetooth file sharing and transfers
cache - Configure web cache settings
clock - Date and Time
colors - Application Color Scheme
componentchooser - Default Applications
cookies - Configure the way cookies work
cursortheme - Mouse Cursor Theme
desktop - Navigation, Number and Layout of Virtual Desktops
desktoppath - Paths to Personal Files
desktoptheme - Desktop Theme
devinfo - Device Viewer
dma - DMA information
emoticons - Emoticon Theme
filetypes - Configure file associations
fontinst - Font Installation, Preview and Removal
fonts - Fonts
formats - Numeric, Currency and Time Formats
icons - Icon Theme
interrupts - Interrupt information
ioports - IO-port information
joystick - Joystick
kcm_activities - Configure the activities system
kcm_baloofile - Configure File Search
kcm_infosummary - Hardware Information Summary
kcm_keyboard - Keyboard Hardware and Layout
kcm_kscreen - Manage and configure monitors and displays
kcm_lookandfeel - Look And Feel
kcm_memory - Memory information
kcm_pci - PCI information
kcm_phonon - Phonon Audio and Video
kcm_plasmasearch - Configure Search
kcm_splashscreen - Splash Screen Theme
kcm_ssl - SSL Versions and Certificates
kcm_useraccount - User information such as password, name and email
kcmaccess - Accessibility Options
kcmkded - Background Services
kcmkwineffects - Desktop Effects
kcmlaunch - Application Launch Feedback
kcmnotify - Event Notifications and Actions
kcmsmserver - Desktop Session Login and Logout
kcmtrash - Configure trash settings
kcmusb - USB devices attached to this computer
kcmview1394 - Attached IEEE 1394 devices
keys - Global Keyboard Shortcuts
khotkeys - Configure Input Actions settings
kwincompositing - Compositor Settings for Desktop Effects
kwindecoration - Look and Feel of Window Titles
kwinoptions - Window Actions and Behavior
kwinrules - Individual Window Behavior
kwinscreenedges - Active Screen Corners and Edges
kwinscripts - Manage KWin scripts
kwintabbox - Navigation Through Windows
mouse - Mouse Controls
netpref - Configure generic network preferences, like timeout values
nic - Network interface information
opengl - OpenGL information
powerdevilglobalconfig - Advanced Power Management Settings
powerdevilprofilesconfig - Energy Saving
proxy - Configure the proxy servers used
screenlocker - Screen Locking Timeouts
scsi - SCSI information
smb - Use to configure which windows (SMB) filesystems you can browse
smbstatus - Samba status monitor
solid-actions - Manage actions available to the user when connecting new devices
spellchecking - Spell Checker Dictionaries and Options
standard_actions - Standard Keyboard Shortcuts for Applications
style - Widget Style and Behavior
translations - No description available
useragent - Configure the way Konqueror reports itself
wayland - Information about the Wayland Compositor
webshortcuts - Configure web shortcuts
workspaceoptions - Workspace Behavior
xserver - X-Server information
Since you still probably have kdebase-workspace, maybe you can fix it with "kcmshell4 icons" instead. -
Collect IDOC into one single XML
Hello All,
I have done IDOC to FILE(XML) scenario.....its working fine..................now client wants to collect the IDOCs and send them in single XML.
Any one done this requirement please help me.
With out using BPM can we achive this requirement.
Thanks and Regards,
ChinnaThanks for the reply.
iam checking the thread which you mentioned in the thread
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1159744050DB00799287682272151265End?blog=/pub/wlg/4443
as in this thread it is mention we have to create the XMLFILE port.
I have already created all the ALE setting like RFC detstination,port (TRFC) and partner profile.
Other then this setting again do i need to create XML FILE port and partner profile.
Please tell me the steps i need to do.
Thanks,
chinna -
Creating cofiles for single system configuration
Hi All,
we have sandbox system where it's congifured like single system in STMS.
when we try to release the requests it's showing local object request number relesed but i am unable to find the cofiles and data files at os end.
Since our system in configured as single system with out target system cofiles will not be created, but i have tried with virtual system and create the transport route but still unable to find the cofiles.
Is there any way to make cofiles available at OS end for single system configuration which having one physical system and one virtual system ....
Please suggest..
Thanks,
Subhash.GHello John,
Please go through my weblog:
<b>Configuring ESS in SAP Enterprise Portal 6.0>
Hope this may solve your problem.
Best Regards,
Srinivas. -
What is the Collection that returns and removes the Object simultaneously
Hi Java Experts,
I believe I'm looking for a Collection that will allow me to (a.) return an object and (b.) remove the object from the collection simultaneously (c) without having to specify the index location of the object. Very similar to what you can do when you enumerate through a Properties Object.
Here is a description of why I think this is the solution that I want. - Perhaps some Design Pattern Experts can help.
I am making an application that is supposed to loop continuously through a collection while adding more information to the collection (example: in a while(collection.size()>0){ take some action })
The action taken inside the while loop would add more items to the collection. I'm hoping that fact would be picked up by collection.size()>0 and cause the iteration to continue.
I am doing this solution within one thread and class. But I'm also going to let this thread feed another Class (A controller thread) with different items which are added to It's collection for it's own loop. That solution will have to handle multiple threads feeding information to it's solution.
Here is example code below of how i'm proposing this would work in a single threaded class.
thanks for all the help
* DESCRIPTION: I want to loop through a collection infinitely by
* making the thread continually add to the collection.
import java.util.*;
public class TESTSOLUTION implements Runnable{
public static void main(String[] arg){
TESTSOLUTION tv = new TESTSOLUTION();
Thread t = new Thread(tv);
t.start();
System.out.println("Finished Main");
public TESTSOLUTION(){
ACollectionType = new TreeSet();
ACollectionType.add("BAT");
ACollectionType.add("BALL");
ACollectionType.add("MIT");
public void run(){
while(ACollectionType.size()>0){
//THIS IS WHERE I WANT TO BE ABLE TO REMOVE AN ITEM FROM THIS COLLECTION
//WITHOUT SPECIFYING THE index
//I just want to call a method and return the object and simultaneously
//remove to the object
outputString((String)ACollectionType.first());
counter++;
private void outputString(String s ){
try{
Thread.sleep(400);
}catch(InterruptedException e){
System.out.println("interrupted");
System.out.println("s = " + s );
//I AM TRYING to add to the object and have the result picked up
// by (perhaps) the ACollectionType.size()>0 method and run the while
// loop infinitly
ACollectionType.add("TOY#"+counter);
private TreeSet ACollectionType = null;
private int counter = 0 ;
}woops here is what i mean --- i got this code to work -- you can run it for yourself .
* DESCRIPTION: I want to loop through a collection infinitely by
* making the thread continually add to the collection.
import java.util.*;
public class TESTSOLUTION implements Runnable{
public static void main(String[] arg){
TESTSOLUTION tv = new TESTSOLUTION();
Thread t = new Thread(tv);
t.start();
System.out.println("Finished Main");
public TESTSOLUTION(){
ACollectionType = new TreeSet();
ACollectionType.add("BAT");
ACollectionType.add("BALL");
ACollectionType.add("MIT");
public void run(){
while(ACollectionType.size()>0){
//THIS IS WHERE I WANT TO BE ABLE TO REMOVE AN ITEM FROM THIS COLLECTION
//WITHOUT SPECIFYING THE index
//I just want to call a method and return the object and simultaneously
//remove to the object
Object ss = ACollectionType.first();
outputString((String)ss);
ACollectionType.remove(ss);
counter++;
private void outputString(String s ){
try{
Thread.sleep(400);
}catch(InterruptedException e){
System.out.println("interrupted");
System.out.println("s = " + s );
//I AM TRYING to add to the object and have the result picked up
// by (perhaps) the ACollectionType.size()>0 method and run the while
// loop infinitly
ACollectionType.add("TOY#"+counter);
private TreeSet ACollectionType = null;
private int counter = 0 ;
} -
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 -
Hi Experts,
I've to insert SAP User Interface inside a custom java portal.
Users should not re-logon when from java portal they pass to CRM User Interface.
I've found that I've to enable ticket logon, but I'm unable to find any documentation that explains how to configure the system to accept ticket logon and permit single sign on.
Could you help me explaining how to solve this requirement?
Thank you
AlessandroHi Shikha ,
this is kumar .... ? I too have the same problem.. I hope you might have find the solution for this problem.. If you have the solution for this problem please send your solutions to this
Email Id: [email protected].
Please help me shikha...
I have this problem
Hi
We have completed configuration of XI.
On the server machine we proceed as follows :
1. We log on to the Integration repository , it askes us for login (userid and password )
2. We enter , say , id as xisuper , with password
3. Now Java Web Start is started and all jar fikles are uploaded automatically
4. Now we get IR page and we can work on it (It is working perfectly )
Now, we proceed on local desktops as follows:
1. We log on to the Integration repository , it askes us for login (userid and password )
2. We enter , say , userid as xisuper , with password
3. Now Java Web Start is started and all jar files are uploaded automatically
4. Now an error popups , saying Single Signon failed and it asks for login and password
Our question is , if it is properly working on server machine , then why is it not working properly on local desktops
Please note that when we launch System Landscape Directory , this problem does not come
Can someone please suggest us a solution
Also we would like to know, which user should we use to access the Integration Repository. Is it the same as the super user ie xisuper or some special user
Or is there some problem with Single signon configuration
Please guide us on this as we need help urgently
Maybe you are looking for
-
Problem with Updating clients with UNIX command
Hi. Until this day, I used to update all our 50 client macs by manually logging in as administrator via ARD and choosing Software Update from the apple menu, this works always and I use our own servers SUS so the downloading is really fast. Still, th
-
Oracle 10g Express Edition for OCP 10g Upgrade Certification
Hi Can I use Oracle 10g Express edition to prepare for Oracle 10g Release 2 new features exam. Thanks, James
-
Customizing Resource Assignment form in IdM
Hi All, I am very new to IdM and have a simple task to do. But can not figure out how. I have two Sql Database table resources. I want to have a situation where: 1. An Administrator Logs into IdM and Searches for an user giving his AcccountId, LastNa
-
See Exclusive Sneak Peek of Jurassic World at Best Buy!
Get ready to return to your favorite park- Jurassic World is coming to Best Buy! Now through June 13th, you can view exclusive Jurassic World content at the Samsung Entertainment Experience Shops located in Best Buy. Get a first look at special foota
-
Avoid the persistance of the data ?
Hi Guys, I am sending the raw credit card data through xi, is there any way to avoid the data storage in xi. I cannot control with user authentications or controlling the access to sxmb_moni. I should avoid the persistance of the data completly or i