Chat now with support
Chat mit Support

erwin Evolve 2020.1.1 - User Guide

erwin_Evolve_User_Guide
erwin_Evolve_User_Guide
Getting Started Creating Sites and Pages Data Layout Options Filtering Data Property Groups Data Visualizations Displaying Diagrams Using Web Modeler Automatic Diagrams (Diagram Designer) Navigating your Site Workflow Explained Social Interaction Features Questionnaires Reference Configuration and Administration Customizing Your Site Troubleshooting Upgrading

Okta Idp Configuration

Configuring SAML2 Authentication and SSO with Okta

If your organization uses Okta (www.okta.com) as an Identity provider, these instructions will help you to configure Single Sign On, between Evolve and your IdP.
 

Create new Application in Okta

1. Select Create new App

2. Platform = Web

3. Sign on Method = SAML2.0

          4. Click create

Configure the Application

1. Provide app name

 

 

          2. General

                    a. Single Sign on URL: Your Evolve URL followed by “/AuthServices/Acs”

Example https://EvolveTest/evolve/AuthServices/Acs

                    b. Ensure “Use this for Recipient URL and Destination UR” is checked

                    c. Audience URI (SP Entity ID): Your Evolve URL followed by “/AuthServices”

Example https://EvolveTest/evolve/AuthServices

                    d. Name ID format: EmailAddress

                    e. Application username: Email

 

          3. ATTRIBUTE STATEMENTS

Add 4 new Attributes

Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

Name Format: URI Reference

Value: user.emailaddress

 

Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

Name Format: URI Reference

Value: user.surname

 

Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

Name Format: URI Reference

Value: user.givenname

 

Name: http://schemas.xmlsoap.org/claims/Group

Name Format: URI Reference

Value: isMemberOfGroupName("Evolve Contributor") ? "Evolve Contributor" : (isMemberOfGroupName("Evolve Social") ? "Evolve Social" : "NO")

IMPORTANT NOTE: in the above value we have specified the name of the Okta Groups in this case the group names are “Evolve Contributor” and “Evolve Social”. These are the Group names you must specify in Evolve Designer.

This States that any user that in in the Okta group “Evolve Contributor” will be passed as a Contributor user and any user in the Okta group “Evolve Social” will be passed as a Social user. Finally any user that is not a member of either Okta groups will be passed as “No” and will gain no access.

 

Accept all other defaults

SAML Meta Data

1.In the Okta Admin Page under “Sign On” you will find the “Identity Provider metadata” link to download you’re the metadata.

Select this link and download it to your evolve server. (Saving the File as a XML file)

 

          2. Place your metadata file on the Evolve server in the following location “C:\Casewise\Evolve\Site”           ensure it’s a XML file)

          3. Now in Evolve Designer under server Configuration/Authentication tab

a.Select Authentication mode to “Saml2”

b.SAML2 Entity id = taken from your Metadata xml File

c.SAML2 Meta url = “~/NAME OF YOU METADATA FILE.xml”

d.Evolve’s url = YOUR EVOLVE URL

          4. Save and Configure IIS

 

Publishing Evolve Site

1. For each model you publish under the deployment of the model you must specify the Okta group names in the “AD Group” Fields this must Match the Okta group Names you have set up along with the Values you specified in the attribute statement

          2. Once set you must save. Then deploy the full site.

Authentication and Active Directory

Authentication and Active Directory

Configure Active Directory Authentication and SSO

Configure Active Directory Authentication and SSO

Active Directory is a commonly used Microsoft standard approach to securing logon to Windows and Web systems. The following section will describe both the pre-requisites and the Evolve configuration required to enable Active Directory (AD) as your authentication provider. It is largely assumed that you are knowledgeable about the configuration of Active Directory.

The instructions below explain how to configure your Evolve Server so that you can use AD as an authentication method to access your sites.

Changes to these settings will require the re-publication of the site.

Pre-requisites for AD authentication:

Before proceeding with the connection, there are some preparatory steps you need to complete, in Modeler, Evolve and in the client’s Active Directory configuration in order for the synchronisation to work.

First let's setup the CW Roles:

1. Launch Model Explorer and create two (2) distinct objects within the CW Role object.
You can create as many roles as you want, but make sure that two of them can be used as generic roles for all incoming users.  For example, you can create a role named “Read-Only Users” (which will ultimately contain all Social Users) and another called “Administrators” (or “Contributors”) (which will ultimately contain all Normal Users).

2. Connecting Roles to CW Views.

At this point, you should connect those default roles to the appropriate views to define which pages each user group will be able to access once logged in.  To do this please refer to the appropriate section of the Evolve user guide (here).

If you choose not to connect any views to the roles, then both roles will be able to view the exact same pages.

Next configure the Client Active Directory:

1. Creating new AD Groups:
You need to arrange with your customer’s system administrator to create two (2) distinct groups within their Active Directory. They can choose to name them anything they want, but should keep those names distinct and recognizable so they can then be connected to Evolve.

2. Adding users to the AD Groups:

The client system administrator should then, in conjunction with your main contact within the client, ensure that the appropriate number of users is added in each group.

 Configure the Active Directory Connection:

1. Change Authentication Mode:
Launch Evolve Designer (in Administrator mode) and choose "Server Configuration". Navigate to the "Authentication" tab. In the Authentication Mode drop-down list, switch the default value (CwAuthentication) to ActiveDirectoryAuthentication.

Configuring the AD Connection Path:

          1. If you have not done so already, import the domain SSL certificate into Windows

          2. Export the certificate to a new *.PFX file

          3. Use the following password to secure the certificate :
                    LQMrnsuLpVAZ9ePd
                    Note that it is not currently possible to choose an alternative password. However the certificate is stored securely on your server, and is not made available                               externally, so this should not pose a concern.

          4. Save the filename: CasewiseAuth.pfx
                    in the folder: c:\Casewise\Evolve\Site\bin 

To configure SAML2 on your Evolve server:

          1. Run Evolve Designer.

          2. On the Evolve Designer Models launcher dialog, click the Server Configuration button.

          The Server Configuration dialog opens.

          3. Configure the settings according to the table below:

 

 Authentication

Authentication Mode

Choose how you want Users to be logged on to Evolve:

Use Saml2 to make Evolve expect a SAML2 authentication

Enable Automatic Logon

Leave un-checked

Domain Short Name

Leave this setting blank.

Use SSL Connection (Active Directory)

Leave un-checked.

AD Connection Path

Leave this setting blank.

AD Port

Leave this setting blank.

AD Group Membership Selection Mode

Leave this setting blank.

AD Connection Username

Leave this setting blank.

Connect to Active Directory Forest

Leave this setting blank.

Domain Exclusion List

Leave this setting blank.

SAML2 Entity ID

This is often found in the metadata.xml file, and consists of the URL that Evolve needs to check authentication.

SAML2 Meta Url

This could be a public URL, a private URL or a local file path. The meta data consists of an XML file that contains the settings for the SAML2 configuration.
e.g. configured for a local file:
~/IDP-QA-Metadata.xml

where the metadata file should be stored in the Site folder

Evolve's Url

Enter the URL to the Evolve home page - e.g.
https://domain.company.com/evolve/

          4. Click Save to save your configuration.

If you make any further changes to the server configuration in this dialog, you must Save again.

At this point it will no longer be possible to logon to Evolve, as the final steps are to configure the permissions based on Claims configured on the Authentication Server, and their mapping to groups on the Evolve server.

To configure Groups and Roles on your Evolve server:

Groups and Roles for SAML2 are configured in exactly the same way as they are for Active Directory. Take a look at this to see how they work. You will find this detail in the "AD Mapping" details of the "Site Level Settings" - "Deployment Node Settings".

 Further instructions for specific Identity Providers:

See here for help on Integrating with Okta Identity Provider.

Sites Explained

Sites Explained

There are two types of Evolve Site - Static Sites and Dynamic Sites. Which type of Site you can deploy depends on the type of license you have for Evolve and what you want your users to be able to do on the Site.

A Static Site is a read-only deployment which displays data from your repository taken at a fixed point in time and is therefore is a great way to communicate your approved model data to a wide audience.

See more about Static Sites

Static Sites have the following features:

Read-only data - users cannot edit any data they see.

Fixed data taken at the time of publication - no live connection to the repository.

Open access - no user login required.

Portability - can be accessed via URL on a web server, or directly as files.

A Dynamic Site shows live data from the repository and requires users to log in to access it. It can be configured to allow users to edit data, and you can control data visibility and permissions with Role-based access.

See more about Dynamic Sites

Dynamic Sites can enjoy all the features offered by Evolve - such as Workflow, Comments, Questionnaires, and Favorites.

In summary, Dynamic Sites offer the following features:

Live data - the Site connects directly to your CW repository showing current data from your model.

Restricted access - Users are required to log in to access the Site, with Active Directory and Windows Authentication supported.

Access Rights - Roles and Access Rights can be used to restrict a User's view of the data and also whether they can edit data using the Site.

Workflow - The Workflow component can be used to implement an Approval procedure for editing data, as well as a Review procedure for validating data.

Social features - Dynamic Sites have the Evolve social features built-in as standard, enabling your users to collaborate using Comments, provide feedback with Questionnaires, and create their own quick links to important pages using Favorites.

For a table comparing the features of Static and Dynamic Sites, see the Site Comparison Chart.

Creating a Site makes changes to your Model's meta model, resulting in new Object Types and Associations being added to the Model.

If you are using Evolve for the first time and want to experiment with creating a Site, we recommend that you create a copy of an existing Model and use that as the basis of your Site.

 Deployment

Evolve Sites should be deployed to a web server machine running Microsoft Internet Information Services (IIS).

What do you want to do?

Create a Site

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen