Skip to Content

Enterprise Account vs Windows Account


Can you please help me to understand, what is the difference between

Enterprise Account and Windows Account created in BO.

Also what is the use of

Concurrent and Named account in BO.


Kavin Raj R

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Mar 25, 2017 at 06:14 PM

    Since Enterprise authentication is the default authentication method for the BI platform, it is automatically enabled when you first install the system. When you add and manage users and groups, the BI platform maintains the user and group information within its database.You can not enable the SSO on enterprise account.

    Windows accounts are not created in the BO.Windows account can map in the SAP BO to enable the single sign on in BI launch. Benefit of this no need to maintain different accounts for application.

    Named users license an individual. The license is with the person. To illustrate this, imagine a company with 3 SAP BusinessObjects BI Platform deployments. John has a named user license. He is now licensed to connect to all 3 of these systems. They also guarantee access – they are not subject to availability of a session on the system.

    CSBLs license a session. Sessions are consumed by individuals. Users that are configured to use CSBL licenses consume a CSBL session with each login. This means if Susie is a CSBL user, and logs in to the BI Launchpad, Live Office, and BI Mobile, then she consumes 3 CSBL sessions. CSBL licenses are specific to a single deployment and cannot be shared across multiple deployments in the way that named user licenses can. Unlike named users, CSBL licenses do not guarantee access to a system. If a system has 25 CSBL licenses, and all of them are consumed, then the next CSBL user that attempts to login will receive an error message

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 27, 2017 at 01:01 PM

    Enterprise logon IDs are created within BO and exist only within BO. You may create an enterprise logon ID that are not associated with logon IDs in any other system. The built-in ID "Administrator" is an example of an enterprise logon. You must set a password in BO that the user will use when logging in with the ID.

    It is possible to map a Windows Active Directory (AD) group to a group in BO. When this is done, new IDs will automatically be created in BO for the members of the AD group (optionally, IDs are created either all at once, or when a user first logs in to BO). When the user logs in to BO, he or she must use their AD password (you do not set or change the password for an AD-mapped logon in BO).

    It is possible (common) to create an enterprise alias for an AD logon in BO. In this case, BO has automatically created a logon for a user that is in an AD group. By creating an alias, the user essentially has two logons - one enterprise and one AD, but they are associated with the same account. The user may log in with either the AD credentials or the enterprise credentials, and will see the same content.

    SSO can be used with either enterprise or AD, but it is easier to set up when using AD.

    Add comment
    10|10000 characters needed characters exceeded