Merge remote-tracking branch 'origin/master' into SAAS-960

Author: osvso

docs/architecture/identity-single-sign-on.md

@@ -1,7 +1,7 @@
 ## Functional overview
 
 The expectations for consumers are set by webshops like Coolblue, Apple, Amazon and Google. Insurance companies can now start to impress users and meet higher
-demands from business and regulation. Onegini's Identity & Single Sign-On solution - as a part of the OneWelcome Identity Cloud - contains components you can
+demands from business and regulation. OneWelcome's Identity & Single Sign-On solution - as a part of the OneWelcome Identity Cloud - contains components you can
 easily add to your existing enterprise architecture. The picture below shows the high-level functionality the platform provides.
 
 ![Architecture overview](./img/overview-identity-single-sign-on.svg)
@@ -40,7 +40,7 @@ LOAs). You can use a market standard like STORK or configure your own levels by:
 
 When you want to give your users the option to login using a second factor like a mobile phone, the user is required to register the device. There are a number
 of possibilities to enable the device registration and handling of second factor authentication. You can either enable your current apps to handle the second
-factor or you can use an existing authenticator app provided by Onegini which provides the functionality for you.
+factor or you can use an existing authenticator app provided by OneWelcome which provides the functionality for you.
 
 ### Authentication / Login
 

docs/architecture/interfaces.md

@@ -1,37 +1,37 @@
-The OneWelcome Identity Cloud has several different (programming) interfaces that are used by clients to customize our solution or integrate our platform into their software. This paragraph explains how Onegini manages these interfaces when releasing new software versions. The general rule is that customers should have the least possible impact when Onegini releases new software versions.  
+The OneWelcome Identity Cloud has several different (programming) interfaces that are used by clients to customize our solution or integrate our platform into their software. This paragraph explains how OneWelcome manages these interfaces when releasing new software versions. The general rule is that customers should have the least possible impact when OneWelcome releases new software versions.  
 
-Everything explained below is to make sure that there are no disruptions due to changes made to the software by Onegini when a new software version is deployed. 
+Everything explained below is to make sure that there are no disruptions due to changes made to the software by OneWelcome when a new software version is deployed. 
 
 # Interface Lifecycle
 
-Onegini will manage its interfaces in accordance with a interface lifecycle. Over time there will be new interfaces, but Onegini will also remove outdated interfaces. Clients will be informed in due time.  
+OneWelcome will manage its interfaces in accordance with a interface lifecycle. Over time there will be new interfaces, but OneWelcome will also remove outdated interfaces. Clients will be informed in due time.  
 
 # Backwards compatibility 
 
-Onegini guarantees that its interfaces remain backwards compatible when releasing a new version of its software. Over time we may break backwards compatibility, but we will only do so after giving multiple notifications that a particular interface version is deprecated. More on deprecation can be read in the next paragraph. 
+OneWelcome guarantees that its interfaces remain backwards compatible when releasing a new version of its software. Over time we may break backwards compatibility, but we will only do so after giving multiple notifications that a particular interface version is deprecated. More on deprecation can be read in the next paragraph. 
 
-The general concept around backwards compatibility for our interfaces is as follows: Each interface is versioned and Onegini will not make breaking changes to existing stable interface versions. 
+The general concept around backwards compatibility for our interfaces is as follows: Each interface is versioned and OneWelcome will not make breaking changes to existing stable interface versions. 
 
-Onegini distinguishes different types of interfaces. For each of these interfaces backwards compatibility is guaranteed in a slightly different way. 
+OneWelcome distinguishes different types of interfaces. For each of these interfaces backwards compatibility is guaranteed in a slightly different way. 
 
 ## Templates
 
-The OneWelcome Identity Cloud uses templates to render the UI in the end-users’ browser. These templates can be modified by either customers or our Professional Services department. To guarantee backwards compatibility on a template version, Onegini will: 
+The OneWelcome Identity Cloud uses templates to render the UI in the end-users’ browser. These templates can be modified by either customers or our Professional Services department. To guarantee backwards compatibility on a template version, OneWelcome will: 
 
 - not rename templates 
 - not rename or remove variables used in templates to fill them with user specific data 
 - not rename or remove variables used to fetch translations 
 
-Onegini can introduce new templates or new variables, or translations to existing templates. These variables or translations are connected with a new feature that, if not enabled, will not impact existing template customizations. 
+OneWelcome can introduce new templates or new variables, or translations to existing templates. These variables or translations are connected with a new feature that, if not enabled, will not impact existing template customizations. 
 
 ## APIs
 
-The OneWelcome Identity Cloud exposes many APIs that allow customers to fully integrate our platform in their software. This also means that Onegini will improve / change these APIs. To guarantee backwards compatibility APIs are versioned and for stable versions we will: 
+The OneWelcome Identity Cloud exposes many APIs that allow customers to fully integrate our platform in their software. This also means that OneWelcome will improve / change these APIs. To guarantee backwards compatibility APIs are versioned and for stable versions we will: 
 
 - not rename or remove fields in the API request or response 
 - not add or remove required fields / parameters in the API request 
 
-Onegini may introduce new parameters or fields in an API request or response, as long as these are not required. This for example means that the software that interacts our APIs must be able to deal with new fields returned in an API response. This is a common practice when consuming APIs. 
+OneWelcome may introduce new parameters or fields in an API request or response, as long as these are not required. This for example means that the software that interacts our APIs must be able to deal with new fields returned in an API response. This is a common practice when consuming APIs. 
 
 ## SDKs
 

docs/architecture/mobile-identity-access.md

@@ -10,7 +10,7 @@ Mobile security has been a complex and investment-heavy feature. Not to mention
 
 ![Architecture overview](./img/overview-mobile-identity-access.png)
 
-On the left-hand side you see your mobile app where the Onegini Mobile Identity & Access solution provides options for Authentication processes like enrollment and strong customer authentication. Within these processes you can use a wide range of authenticators. We natively provide a PIN mechanism and seamless integration with biometric solutions like fingerprint and facial recognition authentication on mobile devices.
+On the left-hand side you see your mobile app where the OneWelcome Mobile Identity & Access solution provides options for Authentication processes like enrollment and strong customer authentication. Within these processes you can use a wide range of authenticators. We natively provide a PIN mechanism and seamless integration with biometric solutions like fingerprint and facial recognition authentication on mobile devices.
 
 On the server side you'll manage and control all the rules and configuration like a pin policy, the applicable mobile OS versions your users have to use or which fallback mechanism between authenticators you allow. Out of the box you can configure a wide range of security features like:
 
@@ -19,11 +19,11 @@ On the server side you'll manage and control all the rules and configuration lik
 - Secure server communication (payload encryption)
 - Secure user authentication
 
-On the right-hand side you see the server side functionality where you provide the apps with data and monitor and control the flows and traffic. The Onegini Mobile Identity & Access solution uses OAuth 2.0 tokens to protect your APIs. This makes sure your customers have access to their resources. 
+On the right-hand side you see the server side functionality where you provide the apps with data and monitor and control the flows and traffic. The OneWelcome Mobile Identity & Access solution uses OAuth 2.0 tokens to protect your APIs. This makes sure your customers have access to their resources. 
 
 ### Passwordless login 
 
-Build on top of our Mobile security offering we offer a whitelabel authenticator app that your can use to offer a secure Passwordless Login experience for your customers and/or employees. The app is ready to go and requires low effort for both developers and the end users. Onegini's Passwordless Login is branded in your company's styling/colors. The user experience is very intuitive and fluent. In all flows of the app, the error handling is included in a user-friendly way. Onegini's Passwordless Login supports App2Web technology, enabling your users to continue their journey as a logged-in user in responsive web pages. 
+Build on top of our Mobile security offering we offer a whitelabel authenticator app that your can use to offer a secure Passwordless Login experience for your customers and/or employees. The app is ready to go and requires low effort for both developers and the end users. OneWelcome's Passwordless Login is branded in your company's styling/colors. The user experience is very intuitive and fluent. In all flows of the app, the error handling is included in a user-friendly way. OneWelcome's Passwordless Login supports App2Web technology, enabling your users to continue their journey as a logged-in user in responsive web pages. 
 
 Out-of-the-box supported flows:
 
@@ -34,4 +34,4 @@ Out-of-the-box supported flows:
 - Support for **NOTIFICATIONS AND TRANSACTION APPROVAL**
 - Over 40 screens with **SELF SERVICE FLOWS AND ERROR HANDLING**
 
-You do not need any employees on your side for maintenance since Onegini will service our technology as a SaaS. Also, you don't have to worry about all Android and iOS updates, or the many new device updates as we will manage this for you.
+You do not need any employees on your side for maintenance since OneWelcome will service our technology as a SaaS. Also, you don't have to worry about all Android and iOS updates, or the many new device updates as we will manage this for you.

docs/dabp/index.md

@@ -13,7 +13,7 @@ This system allows your distribution partners to take care of their own user man
 internal changes (employees leaving, getting promoted, getting certified, reorganizations, etc.). This will significantly lighten the load
 on your B2B support center.
 
-Delegated Administration for Business Partners is offered as an additional feature you can add to your Onegini Identity & Single Sign On
+Delegated Administration for Business Partners is offered as an additional feature you can add to your OneWelcome Identity & Single Sign On
 module.
 It can be configured easily for the needs of different industries and client-types.
 

docs/dabp/release-notes/index.md

@@ -1,8 +1,8 @@
 # Release notes
 
-This section contains release notes for Onegini DABP.
+This section contains release notes for OneWelcome DABP.
 
-In the release notes we mention new features and bug fixes. If anything is unclear, feel free to contact [Onegini Support](https://support.onegini.com).
+In the release notes we mention new features and bug fixes. If anything is unclear, feel free to contact [OneWelcome Support](https://support.onewelcome.com/).
 
 ## Release date: 2023-11-06
 
@@ -128,7 +128,7 @@ In the release notes we mention new features and bug fixes. If anything is uncle
 * The browser title is now customizable
 
 ### Bugs
-* Fixed an issue with internal communications with other Onegini services
+* Fixed an issue with internal communications with other OneWelcome services
 
 ## Release date: 2021-04-28
 

docs/identity-providers.md

@@ -9,19 +9,18 @@ An Identity Provider is a system that creates, maintains, and manages identity i
 The OneWelcome Identity Cloud manages connections to various Identity Providers for your application and sits between your application and the Identity Provider that authenticates your end-users.
 
 - When you use the OneWelcome Identity Cloud as the user store for your applications, users can sign in with their email and password by default.
-- You can add connections to social Identity Providers like Google, Twitter, or Facebook. It allows your users to sign in to your app using credentials from their social accounts. After users authenticate, you sync certain attributes from their social account to an Identity in your Onegini user store, while continuing to use that Identity Provider for user authentication. This eliminates the need to store an additional username and password for that user.
-- You can add connections to predefined federated Identity Providers that are active in our primary markets. The following link contains a [complete list of the Identity Providers that we support](https://www.onegini.com/knowlegde/apis-integrations#identity_proofing).
-- You can add connections to Identity Providers that you have built in-house. As long as these support the OpenID Connect or SAML protocols. This is also sometimes referred to as inbound federation or inbound SAML. The SAML flow is initiated with the service provider (in this case, Onegini) that redirects the user to the Identity Provider for authentication. After authentication, a user is created inside your Onegini user store, and the user is redirected back to your application. As the OneWelcome Identity Cloud allows you to connect your applications via SAML and OIDC, we can also function as a proxy between these protocols for cases where you have (legacy) applications that are incompatible with one of these protocols.
+- You can add connections to social Identity Providers like Google, Twitter, or Facebook. It allows your users to sign in to your app using credentials from their social accounts. After users authenticate, you sync certain attributes from their social account to an Identity in your OneWelcome user store, while continuing to use that Identity Provider for user authentication. This eliminates the need to store an additional username and password for that user.
+- You can add connections to Identity Providers that you have built in-house. As long as these support the OpenID Connect or SAML protocols. This is also sometimes referred to as inbound federation or inbound SAML. The SAML flow is initiated with the service provider (in this case, OneWelcome) that redirects the user to the Identity Provider for authentication. After authentication, a user is created inside your OneWelcome user store, and the user is redirected back to your application. As the OneWelcome Identity Cloud allows you to connect your applications via SAML and OIDC, we can also function as a proxy between these protocols for cases where you have (legacy) applications that are incompatible with one of these protocols.
 
 Adding any of these Identity Providers allows users to sign in to your application using their credentials from a specific Identity Provider.
 
 ## Benefits of using the OneWelcome Identity Cloud to manage Identity Providers
 
-You could connect your application directly to an Identity Provider. However, using the OneWelcome Identity Cloud as the user store for your application and letting Onegini manage the Identity Provider connections has some benefits:
+You could connect your application directly to an Identity Provider. However, using the OneWelcome Identity Cloud as the user store for your application and letting OneWelcome manage the Identity Provider connections has some benefits:
 
 - **No custom code:** Your application only needs to talk to the OneWelcome Identity Cloud.
-- **One protocol:** Your application can use SAML, OpenID Connect, or both to talk to the OneWelcome Identity Cloud. Onegini handles whatever protocols the other Identity Providers uses. This prevents a lot of implementation effort on your side.
+- **One protocol:** Your application can use SAML, OpenID Connect, or both to talk to the OneWelcome Identity Cloud. OneWelcome handles whatever protocols the other Identity Providers uses. This prevents a lot of implementation effort on your side.
 - **Single user store:** All users are stored in the OneWelcome Identity Cloud. You can capture the profile attributes from an Identity Provider user and store those attributes in your Identity Store.
 - **Profile sync:** If a user updates their profile at the Identity Provider, those changes can be reflected inside the OneWelcome Identity Cloud the next time that they use the provider to sign in.
-- **Account linking:** A single end-users can use multiple Identity Providers to sign in, and the OneWelcome Identity Cloud links those profiles to a single user in your Onegini user store.
+- **Account linking:** A single end-users can use multiple Identity Providers to sign in, and the OneWelcome Identity Cloud links those profiles to a single user in your OneWelcome user store.
 - **Identity Proofing:** The OneWelcome Identity Cloud allows you to store a score that represents how sure you are about the real-life identity of an end-user. This gives you a complete overview of how and when a user provided information about their real-life identity.

docs/index.md

@@ -1,7 +1,7 @@
 # OneWelcome Identity Cloud
 
-Onegini was founded in 2011 and supports today over 200 customer labels with over 45 million users spread over multiple countries. With OneWelcome Identity Cloud,
-the company offers an omnichannel Customer Identity and Access Management solution (CIAM) for the banking, insurance and pension industry. With Onegini,
+With OneWelcome Identity Cloud,
+the company offers an omnichannel Customer Identity and Access Management solution (CIAM) for the banking, insurance and pension industry. With OneWelcome,
 organisations quickly and securely create mobile apps and digital portals for consumers, employers and advisors while not having to worry about registration,
 identification, login and management of the digital identity.
 
@@ -33,5 +33,5 @@ Navigate to the single-tenant documentation site on [docs-single-tenant.onegini.
 * Token Server, Security Proxy, and Extension Engine
 * Customer Service
 
-Contact [Onegini Support](https://support.onegini.com/) if you are not sure whether you are on the single-tenant or multi-tenant version of the Onegini Identity
+Contact [OneWelcome Support](https://support.onewelcome.com/) if you are not sure whether you are on the single-tenant or multi-tenant version of the OneWelcome Identity
 Cloud.

docs/messaging-service/index.md

@@ -29,14 +29,19 @@ tenant-specific-folder:
             - messages.properties
             - messages_en.properties
             - messages_pl.properties
-            - messages_otherlocalecode.properties              
+            - messages_nl_BE.properties
+            - messages_otherlangugecode_COUNTRYCODE.properties              
 ```
 
 The Messaging service uses the [Mustache template language](https://github.com/samskivert/jmustache) for templating. Templates can be localized and sent in a
 language specified in the request. All messages files MUST contain all translation keys. The Messaging service does not merge the default file with localized
 files to avoid unnecessary file downloads. The locale must be passed in the request. If no locale is provided, the default file will be used. If no file for the
 provided locale is present, the default file will be used. To include a localized message in the template, the message key should be wrapped in the `{{i18n}}`
-tag. 
+tag.
+
+!!! note
+
+    The requested locale is case-sensitive and must match the messages.properties extension. e.g. if the requested locale is `nl_BE`, it will match the file messages_nl_BE.properties.
 
 ### Example