Skip to main content

i4connected Knowledge Base

Finishing Touches

Abstract

Check out the upcoming articles and learn how to install or configure some further i4connected features, before finishing the installation.

Logging into the Application
Abstract

Check out this article and learn more details on how to log into the system and which credentials you can use for the first use.

After performing all the previously described steps, you can proceed with checking your new i4connected installation, as follows:

  1. Run the Server and open the WebApp.

  2. The i4connected Home page will be opened in your default browser.

  3. Using the following default credentials, please log into the application.

    Tip

    Your default credentials:

    • Username: admin

    • Password: WEBfactory2020!

    Tip

    For more details about the Login page, please also visit the dedicated article, here.

Importing Translations
Abstract

Check out this article and learn how to bring translations into a newly created i4connected database, as a finishing touch of the installation guide.

After a successful login, you can now proceed with importing i4connected translations, as follows:

  1. Identify the Import data tile and click it to open the Import panel. This tile should be available under the Setup page.

    Import_data.jpg

  2. Upload the translation file via the Browse button and select the desired Import type, choosing from the three available options:

    Important

    The Translation file should be requested from the HMS Technical Support team if it has not been provided to you.

    • Append - the translations will be appended to the current data.

    • Overwrite with merge - the current data will be overwritten and merged with the imported translations,

    • Overwrite with replace - the current data will be overwritten and replaced with the imported translations.

  3. To proceed with the translation import, click the Save button. The Import panel will provide you with a pre-validation report, where all the errors will be described.

Installing the API Printing service
Abstract

Check out this tutorial in order to learn how to set up the printing service for your i4connected database and how to install the Chromium software.

The i4connected Printing service is based on the Chromium software so it is recommended to install it on the machine where it is accessible to the ASP.NET Core application. Please follow up the below-described steps in order that you set up your Printing service:

  1. Download Chromium software from here and install it on the machine where the i4connected installation is available.

    Note

    For the present tutorial, we are using the 706915 Chromium version and we downloaded the chrome-win.zip archive.

    chrominum.jpg

  2. Next, open Microsoft SQL Server Manager Studio and connect to the database server. Open the Settings table by means of right-clicking and Edit Top 200 Rows.

    Settings_table.jpg

  3. Identify the feature.printing .executablePath setting.

    Table.jpg

  4. Make sure that the value of the is the feature.printing .executablePath setting is the absolute path to the chrome.exe .

  5. In order to check your settings, open the i4connected application and try to print the contents of a panel, using the designated function.

    Print.jpg

  6. The PDF document will be downloaded directly in the browser.

    PDF_doc.jpg
Installing External Providers
Abstract

Check out this article and learn how to enable multiple external providers such as Facebook, Twitter, Google, Microsoft, and Custom OpenID Connect.

The i4connected application gives users the freedom to choose which Identity Provider they use to sign in to the portal. Before moving on with this guide, let's clarify what is an Identity Provider.

An identity provider is a service that creates and maintains identity information in order to provide authentication services to the i4connected application. This function can significantly reduce sign-in and registration friction, which allows the users to easily access the application without needing to create new passwords or remember usernames.

The i4connected application allows the user to add social authentication connections (such as Facebook or Twitter), as well as build in-house connections (using the Custom OpenID Connect protocol).

Basically, the user can sign in to the i4connected application, using their credentials from the following supported external providers:

  • Facebook

  • Twitter

  • Google

  • Microsoft

  • Custom OpenID Connect

In order to configure an external provider, please follow the below-described steps:

  1. Open a File Explorer window and locate the appsettings.json file under the i4connected Identity folder.

    160f68199dd715.jpg

  2. Open the appsettings.json file using an editor tool.

  3. Under the Authentication line, the supported external providers are listed.

  4. Replace the null value with the requested information and save the appsettings.json file changes.

    External_providers_overview.jpg

Tip

Please also check our tutorial describing the steps needed to enable Login / Logout when using an external provider.

Here are the settings required to enable the i4connected external providers:

Table 1. Facebook provider

Property

Description

AppId

The unique identification number of your Facebook application account.

AppSecret

The secret key of your Facebook application account.



Table 2. Twitter provider

Property

Description

ConsumerKey

The unique identification key of your Twitter application account.

ConsumerSecret

The secret key of your Twitter application account.



Table 3. Google provider

Property

Description

ClientId

The unique number is used to identify your Google account.

ClientSecret

The secret key of your Google account.



Table 4. Microsoft provider

Property

Description

ApplicationId

The unique identification number of your Microsoft application.

Password

The Client secret (application password) consisting of a secret string that the application uses to prove its identity when requesting a token.



Table 5. Custom OpenID Connect provider

Property

Description

AuthenticationScheme

The scheme is used for external sign-out. To enable the external sign-out scheme for the OIDC provider, the user needs to define a scheme, otherwise, the default value will be used and the external sign-out will be disabled.

Tip

The scheme could be anything (such as the name of the external provider or another useful name) providing that spaces and special characters are NOT allowed.

UsePKCE

The Proof Key for Code Exchange allows the user to prevent attacks and to be able to securely perform the OAuth exchange from public clients.

This setting is by default disabled.

Tip

For more details, please also visit this site.

ClientId

The unique number of the client for which all tokens must be issued.

ClientSecret

The secret key of the client.

Authority

The URL is used to identify the client.

Name

The name of the client will be displayed in the application.

ResponseType

The type of response can be:

  • code - The requester would like an Authorization Code to be returned to them.

  • token - The requester would like an Access Token to be returned to them.

  • id_token - The requester would like an ID Token to be returned to them.

  • none - The requester does not want any of the above to be returned to them. The “none” response type is a special case in that it can not be combined with any of the others.

    The other three can be combined in any way, hence requesting all of the details for the combination that was specified. For example:

    • code token - The requester would like both an Authorization Code and an Access Token to be returned to them.

    • code id_token - The requester would like both an Authorization Code and an ID Token to be returned to them.

    • id_token token - The requester would like both an ID Token and an Access Token to be returned to them.

    • code id_token token - The requester would like an Authorization Code, an ID Token and an Access Token to be returned to them.

ResponseMode

The mode of the response can be:

  • query - The Authorization Response parameters are encoded in the query string added to the redirect_uri when redirecting back to the client.

  • fragment - The Authorization Response parameters are encoded in the fragment and added to the redirect_uri when redirecting back to the client.

  • form_post - The Authorization Response parameters are encoded as HTML form values that are auto-submitted in the User-agent, and thus are transmitted via the HTTP POST method to the client, with the result parameters being encoded in the body using the application/x-www-form-urlencoded format.

MetadataAddress

Optionally, allows the user to set a discovery endpoint address for obtaining metadata.

Scopes

Optionally, allows the user to list additional permissions which the i4connected system requests from the external identity provider. For instance, the configured identity provider user email address. The Scopes array should be added between square brackets and each scope should be added between double-quotes.



In this section: