8. Technology development (Tools Git, ngrok)

Technology Development - includes research and development, process automation, and other technology development used to support the value-chain activities.

8.1. The digitization

The digitization is “Digitization, less commonly digitalization, is the process of converting information into a digital (i.e. computer-readable) format, in which the information is organized into bits.”

In short, developing software mimicking manual processes while adding new capabilities such enabling the communication between IT systems from different companies that couldn’t have been integrated using another way.

8.1.1. Digitization for the Insurance industry

# insipried by https://www.celent.com/insights/910618694 # graphviz samples : https://renenyffenegger.ch/notes/tools/Graphviz/examples/index graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; Presentation_layer_1 -- Presentation_layer_2 Presentation_layer_2 -- Business_Logic_Tier_1 Business_Logic_Tier_1 -- Business_Logic_Tier_2 -- Business_Logic_Tier_3 -- Business_Logic_Tier_4 Business_Logic_Tier_4 -- Data_Tier -- Physical_Tier # PRESENTATION LAYER 0 Presentation_layer_1 [shape=house, sides=5, label="Presentation\nlayer", color="blue", style=filled] # PRESENTATION LAYER 1 Chatbot [label="{Chatbot}"] SMS [label="{SMS}"] Robo_advisor [label="{Robo advisor}"] Web_Browser [label="{Web Browser}"] Telephone [label="{Telephone}"] Mobile [label="{Mobile}"] subgraph cluster_Presentation_layer { shape=record Presentation_layer_1 subgraph cluster_Presentation_layer_1 { label=""; rankdir=LR; rank=same; style=dotted; Telephone; Robo_advisor; Mobile; SMS; Web_Browser; Chatbot; }; }; # PRESENTATION LAYER 2 Presentation_layer_2 [shape=house, sides=5, label="Presentation\nlayer", color="blue", style=filled] Broker_portal [label="Broker portal"] Customer_portal [label="Customer portal"] Call_centre [label="Call center"] Middle_office_work_station [label="Middle office\nwork"] Back_office_workstation [label="Back office\nworkstation"] subgraph cluster_Presentation_layer_2 { shape=record Presentation_layer_2 [label="Presentation\nlayer"] subgraph cluster_Presentation_layer_2 { label=""; rankdir=LR; rank=same; style=dotted; Broker_portal; Customer_portal; Call_centre; Middle_office_work_station; Back_office_workstation; }; }; # BUSINES LOGIC 0 Business_Logic_Tier_1 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] # BUSINES LOGIC 1 API_Gateway [label="API Gateway"] subgraph cluster_Business_Logic_Tier_1 { Business_Logic_Tier_1 subgraph cluster_Business_Logic_Tier_1 { label=""; rank=same; style=dotted; API_Gateway; }; }; # BUSINES LOGIC 2 Business_Logic_Tier_2 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] BPM [label="Business\nProcess\nManagement"] BRM [label="Business\nRisks\nManagement"] subgraph cluster_Business_Logic_Tier_2 { Business_Logic_Tier_2 subgraph cluster_Business_Logic_Tier_2 { label=""; rank=same; style=dotted; BPM; BRM; }; }; # BUSINES LOGIC 3 Business_Logic_Tier_3 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] Policy_management [label="Policy management"] Product_management [label="Product management"] Claims_management [label="Claims management"] Customer_management [label="Customer management"] Finance_management [label="Finance management"] subgraph cluster_Business_Logic_Tier_3 { Business_Logic_Tier_3 subgraph cluster_Business_Logic_Tier_3 { label=""; rank=same; style=dotted; Policy_management, Product_management; Claims_management, Customer_management; Finance_management; }; }; # BUSINES LOGIC 4 Business_Logic_Tier_4 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] Quote [label="Quote"] Entreprise_services [label="Enterprises\nservices"]; Policy [label="Policy"]; Products [label="Products"]; Claims [label="Claims"]; Customers [label="Customers"]; subgraph cluster_Business_Logic_Tier_4 { Business_Logic_Tier_4 subgraph cluster_Business_Logic_Tier_4 { label=""; rank=same; style=dotted; Quote; Policy; Products; Claims; Customers; Entreprise_services; }; }; # Data Tier 1 Data_Tier [label="Data\nTier", shape=house, sides=5, color="green", style=filled] Claims [label="Claims"] Policies [label="Policies"] Underwritings [label="Underwritings"] Bills [label="Bills"] Money_collection [label="Money collection"] Products_catalog [label="Products catalog"] CRM [Label="Customer\nRelationship\nManagement"] CDI [label="Customer\nData\nIntegration"] subgraph cluster_Data_Tier { Data_Tier subgraph cluster_Data_Tier_1 { label=""; rank=same; style=dotted; Claims; Policies; Products_catalog; Underwritings; Bills; Money_collection; CRM; CDI; }; }; # Physical Tier 1 Physical_Tier [label="Physical\nTier", shape=house, sides=5, color="brown", style=filled] Servers [label="Servers"] Data_storage [label="Data storage"] Data_centers [label="Data centers"] subgraph cluster_Physical_Tier { Physical_Tier subgraph cluster_Physical_Tier1 { label=""; rank=same; style=dotted; Servers; Data_storage; Data_centers; }; }; label="Digitization of the Insurance industry v2019-09-12"; }

8.1.1.1. Presentation layer

graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # PRESENTATION LAYER 0 Presentation_layer [shape=house, sides=5, label="Presentation\nlayer", color="blue", style=filled] # PRESENTATION LAYER 1 Chatbot [label="{Chatbot}"] SMS [label="{SMS}"] Robo_advisor [label="{Robo advisor}"] Web_Browser [label="{Web Browser}"] Telephone [label="{Telephone}"] Mobile [label="{Mobile}"] subgraph cluster_Presentation_layer { shape=record Presentation_layer subgraph cluster_Presentation_layer_1 { label=""; rankdir=LR; rank=same; style=dotted; Telephone; Robo_advisor; Mobile; SMS; Web_Browser; Chatbot; }; }; }

The presentation layer is the layer that is in connection with your customers through several means or devices :

8.1.1.1.1. Telephone

A service desk supporting the requests on the phone

8.1.1.1.2. Robo advisor

A Robo advisor is a class of financial adviser that provide financial advice or Investment management online with moderate to minimal human intervention

  • The Robo advisor scans and dematerializes your documents
  • The Robo advisor compares the available offers and optimize the portfolio of your customers
  • The customer interacts with the trusted Robo advisors via the web, mobile chat or email
8.1.1.1.3. Mobile or Smartphone

Mobile phones accessing the insurer’ services through SMS, email, voice of mobile app means

8.1.1.1.4. SMS

The customer interacts with the Insurer using SMS. The answers to the SMS are made by a Robo advisor, a Chatbot or a human. The help desks uses an IT system and (s)he is not necessarily answering using a mobile phone.

8.1.1.1.5. Web Browser

a software used to access the Web site of the insurer or the underwriter (i.e. Firefox, Opera, Ecosia, Microsoft Internet Explorer, Google Chrome, Microsoft Edge, Safari)

8.1.1.1.6. Chatbot

The Chatbot is a piece of software that conducts a conversation via auditory or textual methods.

The Chatbot tries to answer customers’ questions that human would have had as a conversation. Some chatbots use sophisticated natural language processing systems but are most of time supported by a service desk run by humans when the Chatbot can’t understand the demands made by the customer.

Chatbot - book a train


graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # PRESENTATION LAYER 0 Presentation_layer_2 [shape=house, sides=5, label="Presentation\nlayer", color="blue", style=filled] # PRESENTATION LAYER 2 Broker_portal [label="Broker portal"] Customer_portal [label="Customer portal"] Call_centre [label="Call center"] Middle_office_work_station [label="Middle office\nwork"] Back_office_workstation [label="Back office\nworkstation"] subgraph cluster_Presentation_layer_2 { shape=record Presentation_layer_2 [label="Presentation\nlayer"] subgraph cluster_Presentation_layer_2 { label=""; rankdir=LR; rank=same; style=dotted; Broker_portal; Customer_portal; Call_centre; Middle_office_work_station; Back_office_workstation; }; }; }

The presentation layer counts the front office as well as the back office. The back office is all the resources of the company that are devoted to actually producing a product or service and all the other labor that isn’t seen by customers, such as administration or logistics.

8.1.1.1.7. Back office workstation

Those are the collaborators managing the operations ensuring the correct exection of the processes :

  • quote an offer
  • validate personal data
  • validate the filling of a form
  • perform the dunning services duties

The back office requires documentation, software and reports to perform their duties.

8.1.1.1.8. Middle office workstation

The middle office is made up of the risk managers and the information technology managers who manage risk and maintain the information resources.

  • Track claim settlement times
  • Customer satisfation ratings
  • Long-term trends in customer activity

Data collected during the operations are stored into IT systems operated by a multitude of managers (risks, operations, HR, Marketing)

Those data are analysed and supports the value chain (logistics, operations, marketing, sales, support) by giving a broad and exact view of the financial situation of the company.

After a careful analysis, the data are shared with the back office who can act and interact with prospects, customers and suppliers depending on the situation (dunning service, quotation, billing, closing off the contract)

Tip

Try the Insurance claims analysis dashboard

Middle office: Insurance Claims Analysis (credits: syncfusion.com)

8.1.1.1.9. Call centre

Three types of call centres might be operated by a financial service company:

  • An inbound call center is operated by a company to administer incoming product or service support or information enquiries from consumers.
  • An outbound call center is operated for telemarketing, for solicitation of charitable or political donations, debt collection, market research, emergency notifications, and urgent/critical needs blood banks.
  • A contact center, further extension to call centers administers centralized handling of individual communications, including letters, faxes, live support software, social media, instant message, and e-mail.
8.1.1.1.10. Customer portal

A website accessible through a Web browser or a mobile phone enabling the customer to access all the aspects of his duties and rights towards the insurer.

The portal gives access to diverse functionalities:

  • Information platform: share details about the products and services, how to contact the insurer

  • Transaction platform: create, update or delete information, stop a current insurance, pay electronically the remaining Bills

  • Sales platform: generate up-sell and cross-sell opportunities, promote the Robo advisor capabilities

  • Rewards platform: Insurers retain their customers through the Perceived Value of the customer, the Affinity that the customer has with his insurer, and the Barriers to Exit

    • Perceived value: does the customer feels that (s)he has coverage at a competitive and fair price?
    • Affinity: do the customer has a emotional connection with the customer? Insurance products may tend to have a limited value due to the commoditized nature of the product
    • Barriers to Exit: does the customer has strong and effective reasons to do not leave an insurer? the lack of competition, the increase of costs, the loss of a unique protection, a decrease of the quality of service
8.1.1.1.11. Broker portal

A broker portal is a website enabling the broker to perform her/his duties

  • Information platform: share details about the products and services, how to contact the insurer, the customers
  • Sales platform: support the sales process (from a quote to a signed contract), generate up-sell and cross-sell opportunities
  • Marketing platform: identify new sales opportunites by advertising the products and identify the most profitable or potential prospects
  • CRM platform: maintain data related to the prospects and customers (contact details, online and offline interactions)
  • Dunning service platform: inform and give the tools to enable the broker to run after unpaid invoices till the termination of the contract

8.1.1.2. Business logic tier

graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # BUSINES LOGIC 0 Business_Logic_Tier_1 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] API_Gateway [label="API Gateway"] subgraph cluster_Business_Logic_Tier_1 { Business_Logic_Tier_1 subgraph cluster_Business_Logic_Tier_1 { label=""; rank=same; style=dotted; API_Gateway; }; }; }

8.1.1.2.1. API Gateway

The API describes the functions or the interfaces available between a client and a server.

APIs are enablers of the platform economy, and allow users to enhance and add services over existing products.

For example: An API enables an application ‘A’ to query a system ‘B’ and collects the schedule of the public transportation (See https://opendata.stib-mivb.be/store/data)

Tip

Look at the description of the API from a dunning Service https://dunningcashflow-api.azurewebsites.net/swagger/index.html

API Documentation: example of a Dunning service


graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # BUSINES LOGIC 2 Business_Logic_Tier_2 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] BPM [label="Business\nProcess\nManagement"] BRM [label="Business\nRisks\nManagement"] subgraph cluster_Business_Logic_Tier_2 { Business_Logic_Tier_2 subgraph cluster_Business_Logic_Tier_2 { label=""; rank=same; style=dotted; BPM; BRM; }; }; }

8.1.1.2.2. Business Risk Management

The financial services must comply with a multitude of risks.

Here are a list of pure risks (loss or no loss only) that an insurer or a underwriter may be confronted with:

  • Regulatory Compliance: Invoice compliance, MiFID ii, MiFID 2, Solvency II, Solvency 2
  • Tax Compliance: Tax determination, Fiscal reporting, VAT reporting
  • Liability risk exposure: product liability risks, or contractual liability risks
  • Operational risk: mistakes in process and procedure
  • Intellectual property violation risk
  • Mortality and morbidity risk at the societal and global level

Warning

  • Speculative risks are not described in this documents. i.e. market risk, reputational risk, brand risk, product success risk…
8.1.1.2.3. Business Process Management

The Business Process Management is a discipline aimed at managing all aspect of the business processes; from process design to modeling and analysis to execution and improvement.

Note

Here is the description of a process: Data entry of a claim

digraph insurance_claim_data_entry { label="Insurance: Claim data entry" ratio="fill"; size="8.3,11.7!"; node [rankdir=LR]; start [label="Start", shape=box, style=rounded] a_claim_is_received [label="A claim is received"] is_it_new_claim [label="Is it a new claim?", shape=diamond] data_entry [label="Data Entry", shape=parallelogram] is_it_correctly_filled [label="Is it correctly filled?", shape=diamond] exception [label="Exception"] end [label="End", shape=box, style=rounded] administrative_worker [label="Back-end worker"] exception [label="Back-end worker\ndeals with the\nexception", shape=parallelogram] amend_data [label="Amend data", shape=parallelogram] start -> a_claim_is_received a_claim_is_received -> is_it_new_claim is_it_new_claim -> data_entry [label="Yes"] data_entry -> administrative_worker [label="The claim is\ndistributed"] administrative_worker -> is_it_correctly_filled [label="Submits the\n new claim"] is_it_new_claim -> amend_data [label="No"] amend_data -> is_it_correctly_filled [label="Submits the claim"] is_it_correctly_filled -> exception [label="No"] exception -> end is_it_correctly_filled -> end [label="Yes"] {rank=same; data_entry amend_data} }


graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # BUSINES LOGIC 3 Business_Logic_Tier_3 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] Policy_management [label="Policy management"] Product_management [label="Product management"] Claims_management [label="Claims management"] Customer_management [label="Customer management"] Finance_management [label="Finance management"] subgraph cluster_Business_Logic_Tier_3 { Business_Logic_Tier_3 subgraph cluster_Business_Logic_Tier_3 { label=""; rank=same; style=dotted; Policy_management, Product_management; Claims_management, Customer_management; Finance_management; }; }; }

8.1.1.2.4. Finance management
8.1.1.2.5. Customer management
8.1.1.2.6. Claims management
8.1.1.2.7. Product management
8.1.1.2.8. Policy management

graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # BUSINES LOGIC 4 Business_Logic_Tier_4 [label="Business\nLogic Tier", shape=house, sides=5, color="red", style=filled] Quote [label="Quote"] Entreprise_services [label="Enterprises\nservices"]; Policy [label="Policy"]; Products [label="Products"]; Claims [label="Claims"]; Customers [label="Customers"]; subgraph cluster_Business_Logic_Tier_4 { Business_Logic_Tier_4 subgraph cluster_Business_Logic_Tier_4 { label=""; rank=same; style=dotted; Quote; Policy; Products; Claims; Customers; Entreprise_services; }; }; }

8.1.1.2.9. Customers
8.1.1.2.10. Claims
8.1.1.2.11. Products
8.1.1.2.12. Policies
8.1.1.2.13. Entreprise services
8.1.1.2.14. Quotes

8.1.1.3. Data tier

graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # Data Tier 1 Data_Tier [label="Data\nTier", shape=house, sides=5, color="green", style=filled] Claims [label="Claims"] Policies [label="Policies"] Underwritings [label="Underwritings"] Bills [label="Bills"] Money_collection [label="Money collection"] Products_catalog [label="Products catalog"] CRM [Label="Customer\nRelationship\nManagement"] CDI [label="Customer\nData\nIntegration"] subgraph cluster_Data_Tier { Data_Tier subgraph cluster_Data_Tier_1 { label=""; rank=same; style=dotted; Claims; Policies; Products_catalog; Underwritings; Bills; Money_collection; CRM; CDI; }; }; }

8.1.1.3.1. CDI (Customer Data Integration)

CDI

8.1.1.3.2. CRM (Customer Relationship Management)

CRM

8.1.1.3.3. Products catalog
8.1.1.3.4. Money collection
8.1.1.3.5. Bills
8.1.1.3.6. Underwritings
8.1.1.3.7. Policies
8.1.1.3.8. Claims

8.1.1.4. Physical tier

graph digitization_insurance { ratio="fill"; size="8.3,11.7!"; node [shape=record, fontsize=16, rankdir=LR]; # Physical Tier 1 Physical_Tier [label="Physical\nTier", shape=house, sides=5, color="brown", style=filled] subgraph cluster_Physical_Tier { Physical_Tier subgraph cluster_Physical_Tier1 { label=""; rank=same; style=dotted; Servers; Data_storage; Data_centers; }; }; }

8.1.1.4.1. Data Centers
8.1.1.4.2. Data storage
8.1.1.4.3. Servers

8.2. GIT lifecycle

Description of how to manage the versions, branches in a git repository as well the operations of the software

How to write relevant commits?

8.2.1. A successful git branching model

A successful Git branching model : https://nvie.com/posts/a-successful-git-branching-model/

By Vincent Driessen on Tuesday, January 05, 2010

8.2.2. GIT : commit conventions

source : conventional commits : https://github.com/conventional-commits

Semantic messages: http://seesparkbox.com/foundry/semantic_commit_messages

build
chore (maintain i.e. updating grunt tasks etc; no production code change)
ci (continuous integration)
docs (documentation)
feat (feature)
fix (bug fix)
perf (performance improvements)
refactor (refactoring production code)
revert
style (formatting, missing semi colons, …)
test (adding missing tests, refactoring tests; no production code change)

8.2.3. GIT : how to manage the versions, branches … ?

  • GIT : Create a branch : [BRANCH-DEV] – [BRANCH-PARENT]

  • DEV : Local development on Software engineer machine

  • MERGE GIT : Merge the [BRANCH-DEV] with the [BRANCH-PARENT]

    • The code is merged into the [BRANCH-DEV]
  • STAGING : The Software is deployed on the staging environment

  • MERGE GIT : Merge the [BRANCH-DEV] with the [BRANCH-PARENT]

    • The code is merged into the [BRANCH-PARENT]
  • PROD : Test the PROD version of the software

  • LIVE : deploy the PROD version of the software on the PROD server

8.2.4. GIT LFS Large File System

  • git commands
  • Install git lfs https://git-lfs.github.com
  • Locks
    • git lfs lock images/foo.jpg
    • git lfs locks
    • git lfs unlock images/foo.jpg
  • git lfs push origin master –all

8.2.4.1. Create a .gitattributes file

.. include:: .gitattributes

8.2.4.2. Commands to add files into the repository, and push the code

git lfs install
git lfs track "*.jpg" --lockable
git lfs track "*.JPG" --lockable
git lfs track "*.png" --lockable
git lfs track "*.zip" --lockable
git lfs track "*.mp4" --lockable
git lfs track "*.MP4" --lockable
git lfs track "*.docx" --lockable
git lfs track "*.svg" --lockable
git lfs track "*.gif" --lockable
git lfs track "*.psd" --lockable
git lfs track "*.sketch" --lockable
git lfs track "*.ai" --lockable

git add "*.jpg" "*.JPG" "*.png" "*.zip" "*.mp4" "*.MP4" "*.docx" "*.svg" "*.gif"

git lfs ls-files
git lfs env

git config lfs.https://inlsprl.visualstudio.com/[ProjectName]/_git/[ProjectName].git/info/lfs.locksverify true
git push origin master
git lfs push origin master --all

8.3. ngrok - Public URLs for exposing your local web server

Use ngrok to grant access to your localhost to anyone

  1. Install https://ngrok.com/download

  2. open the port where the web server is located. run the following command :

    1. [path to ngrok]\ngrok.exe http [port to open on your localhost] -host-header=rewrite
  3. share the URL to the person who needs to access your local machine. i.e. https://a1cc816e.ngrok.io

ngrok by @inconshreveable

Session Status online Account [the account name] (Plan: Free) Update update available (version 2.2.8, Ctrl-U to update) Version 2.2.3
Region United States (us) Web Interface http://127.0.0.1:4040
Forwarding http://a1cc816e.ngrok.io -> localhost:4624 Forwarding

https://a1cc816e.ngrok.io -> localhost:4624

8.4. How to write a bug report?

  1. Copy paste the content hereunder
  2. Create a new issue: https://bitbucket.org/altf1be/software-architecture/issues/new
## WHAT STEPS WILL REPRODUCE THE PROBLEM?

1. Open the page
2.
3.

## WHAT IS THE EXPECTED OUTPUT?

*  StratEx is loaded


## WHAT DO YOU SEE INSTEAD?

* The screenshot attached to this email
* StratEx cannot be opened because of a problem

## WHAT VERSION OF THE PRODUCT ARE YOU USING?

* Version: 3.5.6245.20028
* on [https://www.stratexapp.com](https://www.stratexapp.com)
* on [https://staging.stratexapp.com](https://staging.stratexapp.com)
* on [https://develop.stratexapp.com](https://develop.stratexapp.com)


## ON WHAT OPERATING SYSTEM, BROWSER, ETC.?

* Windows 7.1
   * Chrome Version 54
   * Internet Explorer 11
   * Opera Version 41
* Windows 10
   * Internet Explorer
   * Edge
* Mac OS X 10.9 (13A603)
   * Safari Version 7.0 (9537.71)
   * Chrome Version 31.0.1650.57

## PLEASE PROVIDE ANY ADDITIONAL INFORMATION BELOW.

* None
* Extra files are available on [StratExApp files on Google Drive]
* Find the private [Videos generated on GDrive]
* Find the public [Videos on StratEx YouTube channel]
* Find the public [Documentation on Read The Docs]

## Bug report (if any)

* None

[StratExApp files on Google Drive]: https://drive.google.com/a/alt-f1.be/folderview?id=0B9L2cx0TUjLGUFZBSkF6WlFCYms&usp=sharing#list
[Videos generated on GDrive]: https://drive.google.com/a/alt-f1.be/folderview?id=0B9L2cx0TUjLGa190N1ZURHBpUFE&usp=sharing
[Videos on StratEx YouTube channel]: https://www.youtube.com/channel/UCuwGfoVoozq0ZTmHJ3WCvTQ
[Documentation on Read The Docs]: http://stratexapp-docs.readthedocs.org/en/latest/

8.5. Research & Development topics

  1. Prerequisite:

  2. Single Page Application (SPA)

    • Build a SPA such as Microsoft Azure for our customers
    • Test SPA App
  3. IT Automation best practices

  • Security

8.6. Open Authentication (OAuth)

OAuth is an open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords.

Source: Wikipedia contributors. (2019, March 19). OAuth. In Wikipedia, The Free Encyclopedia. Retrieved 12:20, March 23, 2019, from https://en.wikipedia.org/w/index.php?title=OAuth&oldid=888559139

8.6.1. Use case for Open Authentication

A user requires access to a resource on a web application (eg StratEx) using her credentials from another website (eg Microsoft Office365).

  1. She needs to login using the form from Office365
  2. Office365 will generate a token
  3. The token is used by StratEx ensuring that the user is effectively logged using her Office365 credentials
  4. StratEx can use the resources made available by Office365 such as username, firstname, lastname, email address, read access to OneDrive, write and send new emails…

8.6.2. Open authentication using Office365

Microsoft graph documentation makes available Office365 resources of each registrered user:

Request an access token to Office 365:

Description of each parameter (see use-the-authorization-code-to-request-an-access-token):

  • https://login.microsoftonline.com/common/oauth2/v2.0/authorize
  • ? client_id =f5d835b0-4bc1-98e7-f98cb4aaef31
  • & scope =https%3A%2F%2Fgraph.microsoft.com%2Fuser.read
  • & response_type =code
  • & redirect_uri =https%3A%2F%2Ftimesheet-stg-inlsprl.azurewebsites.net%2Fsignin-microsoft
  • & state =Ao8m01yi1E76wQIXPJW-F92Fq1v