Showing posts with label single sign on. Show all posts
Showing posts with label single sign on. Show all posts
Tuesday, June 28
Single Sign On for Non-SAP Applications
Single sign on is possible for external applications also. By external applications, I mean non sap Application. So the scenario is that a user wants to logon to a non sap application from SAP EP without entering user ID and password. Is this possible? The answer is yes. This is possible by implementing SSO for external usage.
There are 2 ways to implement SSO for external usage.
The Dynamic link library SAPSSPEXT is a very intelligent library. It can extract user id and password from the logon ticket issued by SAP EP. So by using this library logon to external or non sap applications is possible. This library has 2 interfaces viz: JNI Java Interface and a COM(Windows) interface. It is available to be downloaded on the sap service marketplace.
Now suppose you have a non-sap applications which is web based and it supports authentication using a HTTP header variable, Web Server Filter method of single sign on is the best for you. This filter studies the logon ticket using a public-key certificate and tries to extract the name of the authenticated user from the logon ticket. This name is then written in the HTTP header variable. Thats it !
Only few web servers support this method of logon. Some of them are Apache Web Server, Microsoft Internet Information Server (IIS), Sun Java System Web Server.
No Need to Remember SAP System Passwords - Implement SSO
What is SSO ?
As the name suggests, single sign on is a feature of SAP EP which enables users to logon to multiple systems during a sessions using only one username and password. SAP EP has various applications integrated into it and users can access those applications. These applications connect to various backend systems. Each system may have login credentials. But when a system is created in SAP EP and user is logged to SAP EP and tries to access data from a system, he not required to logon to that system again if single sign on is configured in the SAP Enterprise portal.
So how do we implement SSO in SAP EP?
There are 2 methods to do it:
1. Using User mapping and
2. Using logon tickets. Logon tickets method is recommended by SAP.
User mapping
User mapping can be used when the system is not able to accept the logon tickets. So the mapping is done between the portal ID and user-id and password of the target system. It is not necessary that portal logon id and ECC system logon id are same.
To create a SSO, you need to create a system in portal. Then you need to set various necessary properties of the system created. The logon method property of the system must be set to UIDPW. Also you need to set user mapping to access SAP ECC.
During single sign, secure information that is the user ID and password of the user are sent across network, so a secure protocol for the communication must be used. Recommended is secure socket layer protocol.
Logon tickets
Logon tickets are essentially ticket of user credentials and not the actual user credentials. They do not contain any passwords. This ticket is issued by the portal server after the user has logged in successfully. This ticket is stored in user’s local machine or client as a cookie. Then it can be used by the external applications like SAP systems to logon. Logon ticket may contain portal user ID and a mapped user ID for logging on to external applications. It contains the valildity period, it contains the information which identifies the system which issued the logon ticket. It also may contain digital signature.
Single Sign On for Non-SAP Applications
Related Posts :
Save Costs, Time, and Efforts-install Business Packages
What Is an Enterprise Portal?
Single Sign On for Non-SAP Applications
Related Posts :
Save Costs, Time, and Efforts-install Business Packages
What Is an Enterprise Portal?
Sunday, June 26
Instant start to Netweaver portal administration
This post will provide you a basic and instant start to Netweaver portal administration. Definitions of the most important things that you much know for portal administration are covered in this post.
Usage Types
Before I tell you what are usage types, I must tell you that usage types made a SAP Portal administrator's life easy. Usage types were introduced when SAP Came up with SAP Netweaver Portal 7.0.
Usage types of SAP NetWeaver are software units to be installed. The usage types Application Server ABAP and Application Server Java are used as a foundation for other units. You can select one or more usage types during NetWeaver installation.
SLD
If you are a portal administrator you must know how to configure SLD. This can be done manually also and there is an automated way of doing this. You can chose one depending on your situation and requirements.
The SLD configuration is included in the AS Java installation. In some cases, the SLD configuration has to be changed. Below are main steps to be followed while changing the SLD Configuration.
- Specify the Groups and Users That Can Operate in the SLD
- Specify Where to Persist the SLD Information and Who Can Alter It
- Fine Tuning the SLD Server
- Initial Import of the SAP CIM model or the CR Content
- Configuring the Channel for Receiving SLD Reports
JCO
JCO or the Java Connectors connect SAP EP applications to SAP R/3 systems. So basically they fetch data and functionality from the SAP systems to be used and displayed in SAP EP or in applications which are used by SAP EP. For example, SAP Web Dynpro Java applications can talk with the SAP systems using JCO. As a portal administrator, you must know how to created, edit, check and activate a JCO. How to delete a JCO, how to troubleshoot a JCO in case of errors in connection.
Properties of Iview, workset and roles
Various properties of Iviews, worksets, roles are a must to know. This is important when administrator is asked to create/modify these PCD objects. Based on various business requirements, portal administrator may have to change the properties at runtime or design time and achieve what is needed.
Admin Tools
Various tools like Visual admin, Config tool and offline config editor are must.
SSO and System Configurations
Single Sign On means that portal user will have to punch in his/her username and passord only once and after that he/she will not be asked for login credentials no matter which system he/she tries to access through portal. This feature of SAP Netweaver portal helps you a lot by providing you the freedom to forget passwords. SAP EP connects to various backend SAP systems on your behalf. It is very important topic to be known by a portal administrator. Frequently asked in interview questions. How to create a SSO. How to change SSO settings etc etc...
Subscribe to:
Posts (Atom)