deepak.r

Like flowcharts, BPMN (Business Process Model and Notation) diagrams uses a set of standard symbols. Each shape conveys a specific meaning and business context, where it’s most appropriate. Connecting objects are lines, that connect the BPMN flow objects. In Business Process Model and Notation, different connecting objects are required to represent different types of flows. There are three different types of connecting objects in Business Process Model and Notation. They are

The building blocks of BPMN are 'Flow objects'. which represents the concepts of being modeled. Flow elements refer to the elements, that form a complete process flow when connected are connected. Connectors that connect the flow elements are called connecting objects. Readers of the BPD follow the flow of elements to see, how a business process gets executed and completed. Flow objects can be separated into three. They are events, activities, and gateways.

The term 'Events' represents the events in a business process. Specific details in a process can be represented by styling each event. There are three event type in business process, they are start events, intermediate events, and end events. Following are the event symbols contained with start event, which can be combined with any event type. Some commonly used event symbols are following BPMN Message Symbol

When a user is successfully authenticated to OpenAM, a session will be generated in the server. Sessions generated in the server are identified by a unique token, named SSOtokenID. The SSOToken is a C66Encoded string, that points to the session in memory, and the Session Key is a Base64 Encoded string that is used to identify the location of the site and the server where the session is maintained. There is a period delimiter that separates the SSOToken and session key. As the session key is a Base64 encoded string, we can decode it using any Bas64 decoders.

Today's Internet world, urges Single Sign On for multiple web applications as an inevitable requirement. It's not an easy task to implement SSO (Single Sign On), if the web applications are developed on different platforms. User authentication and maintenance of user's "logged in session" on web applications, is completely dependent on HTTP cookies. No web browsers allow to read cross domain cookies, as if it allows, it's a security issue then. I.e; Two web applications cannot share a single cookie, if they are deployed in different domains.

LDAP stands for Lightweight Directory Access Protocol, which was designed to store and retrieve data centrally. Install OpenLDAP and phpLDAPadmin, before reading the configuration steps. Hope the packages were already installed, we can start configuring a few things, to connect with the OpenLDAP directory structure, created during the LDAP configuration stage. First, we can update the main configuration file with root privileges for the editor

LDAP stands for Lightweight Directory Access Protocol, which was designed to store and access data centrally. It can be used to store any kind of information, but usually, it is used for a centralized authentication system (SSO). In some cases, it works similarly to relational databases. The main difference is the hierarchical structure in data relation. To install LDAP in your Ubuntu machine, do the following steps.