developing for next gen identity services

18
2013 Open Stack Identity Summit - France Developing for Next Gen Identity Services Jake Feasal, UI Lead Jonathan Scudder, OpenAM Architect

Upload: forgerock

Post on 10-May-2015

936 views

Category:

Technology


0 download

DESCRIPTION

Presented by Jonathan Scudder, OpenAM Architect and Jacke Feasel, UI Lead, ForgeRock

TRANSCRIPT

Page 1: Developing for Next Gen Identity Services

2013 Open Stack Identity Summit - France

Developing for Next Gen

Identity Services

Jake Feasal, UI LeadJonathan Scudder, OpenAM Architect

Page 2: Developing for Next Gen Identity Services

Once upon a time...

Open Source

Simple API

Page 3: Developing for Next Gen Identity Services

Growth

ScaleWell understood technology

Page 4: Developing for Next Gen Identity Services

Roll-out

Commonality

Integration

Page 5: Developing for Next Gen Identity Services

Product ‘suite’

Page 6: Developing for Next Gen Identity Services

Common REST API

• Open Source

• REST (JSON, SCIM++)

• ROA

• JASPIC

Page 7: Developing for Next Gen Identity Services

ROA + REST + JASPIC

• Resources vs services• Users, Groups, Realms, Sessions, Tokens...

• Granular control

• Standard set of operations

• Flexible authentication and authorization

Create

Read

Update

Delete

Patch

Action

Query

Page 8: Developing for Next Gen Identity Services

ForgeRock developers

Page 9: Developing for Next Gen Identity Services
Page 10: Developing for Next Gen Identity Services

API strategy - stack

Page 11: Developing for Next Gen Identity Services

Problem

Too many different complicated UI Frameworks

Roots from sun

Big company UI strategy churn

Developers learning new frameworks

Customers are locked in

Simple modifications overly complex

Leads to heavyweight API just for the UI

Page 12: Developing for Next Gen Identity Services

Legacy User Interfaces

YUI/Click

Jato

JSF/Ice Faces

JSP Admin

Java Swing

Page 13: Developing for Next Gen Identity Services

Open Identity Stack UI Model

“Single-Page Web App” style

Single UI model for all products

Built on ForgeRock REST (CREST)

Common UIs for:

User management

Registration and Self Service

Login and Password Reset

Build on shared services for Authentication

Page 14: Developing for Next Gen Identity Services

ForgeRock UI Library Stack

jQuery (General utility) + jQuery UI (Widgets)

Backbone.js + Require.js (Modular MVC Architecture)

Handlebars.js (Templating)

Underscore.js (General utility)

Less.js (CSS preprocessor)

Built on ForgeRock REST and Common Services

Caters to the web developers of today

Two different models for ForgeRock UIs

Page 15: Developing for Next Gen Identity Services

Admin and Configuration

Used primarily by Administrators

UI not typically customized

Configuration for product services

Dynamically rendered based on server JSON schema

REST APIs for custom applications

Adding new services dynamically rendered

Customers not expected to modify more than CSS

Page 16: Developing for Next Gen Identity Services

End User

Primarily seen by end users Simple HTML Templates

Read in by Javascript and embedded in the UI

Rendered with site wide styles/CSS

Simple syntax for embedding dynamic values

Separates bus logic from display

Simple to modify without breaking the UI

Easy to patch and upgrade

Page 17: Developing for Next Gen Identity Services
Page 18: Developing for Next Gen Identity Services

Q & A

Logo of Presenter Company HERE