Skip to content
An example demonstrating usage of SDKs
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Big update (#26) Apr 6, 2018
.vscode Big update (#26) Apr 6, 2018
browser FIx lint. May 22, 2019
docker Big update (#26) Apr 6, 2018
scripts Big update (#26) Apr 6, 2018
.dockerignore Big update (#26) Apr 6, 2018
.editorconfig Big update (#26) Apr 6, 2018
.env-template Big update (#26) Apr 6, 2018
.eslintignore Big update (#26) Apr 6, 2018
.eslintrc.yml Big update (#26) Apr 6, 2018
.gitignore Big update (#26) Apr 6, 2018
.travis.yml Big update (#26) Apr 6, 2018
CHANGELOG.md Bump account-sdk version, and sdk-example version May 14, 2019
CODE_OF_CONDUCT.md Big update (#26) Apr 6, 2018
CONTRIBUTORS.md Big update (#26) Apr 6, 2018
LICENSE.md Big update (#26) Apr 6, 2018
NOTICE Big update (#26) Apr 6, 2018
README.md Big update (#26) Apr 6, 2018
app.js Add some routes for common icon stuff Sep 25, 2018
asyncMW.js Big update (#26) Apr 6, 2018
build.sh Big update (#26) Apr 6, 2018
config.js Allow testing payment flow for alternative client. May 14, 2019
example_csr.pem Big update (#26) Apr 6, 2018
example_key.pem Big update (#26) Apr 6, 2018
example_server.crt Big update (#26) Apr 6, 2018
filterExt.js Big update (#26) Apr 6, 2018
oauth.js Big update (#26) Apr 6, 2018
package-lock.json
package.json bump version May 23, 2019
server.js Big update (#26) Apr 6, 2018
watch.sh Try to improve ‘npm run dev’ Jun 22, 2018

README.md

SDK Example

Build Status

Introduction

This is a demonstration of how a client can use the Schibsted Account login flows. You can see it live at:

Its main intention is code as documentation and is intentionally simplified to demo the most important steps for using the SDK.

Take a quick look at its browser code in index.js and its server code in app.js.

Installation

  1. Clone this repo
  2. Run npm install.

Configuring the server

  1. You need a few configs obtained from self service in the right environment in order to get started. Set your Identity client credentials in the .env file in the root folder. To get a head start you can just copy a template that's already included in the repo (run: cp .env-template .env and fill in the blanks. Take a look at .env-template to see what is needed.
  2. Then do a source .env && npm start.

VSCode batteries included

If you're using VS Core it's super easy. Just choose the debug menu and launch "SDK-Example-DEV". It's automatically load the configuration from the .env file you created previously.

You can’t perform that action at this time.