- Manage service plans via https://p-identity.systemdomain and make sure your org can use this service
- connect to your new sso instances dashboard by going to apps manager -> org -> serivces -> sso instance -> manage
The power
resource should have the following permissions granting the frontend apps access to your super powers
- power.fly
- power.strength
- power.invisibility
Edit environment variable HEROSERVER
with your app domain. This allows the frontend apps to find the hero server resource. Also feel free to change the appname from hero
to what ever you like, but make sure this url is updated accordingly.
env:
HEROSERVER: http://hero.<APP DOMAIN>
cf push -f manifest.yml
Frontend Apps:
- sso-hero-web
- Uses
authoriation_code
grant type
- Uses
- sso-hero-mobile
- Uses
password
grant type
- Uses
- sso-her-implicit
- Uses
implicit
grant type
- Uses
Backend App:
- hero
- Uses
client_credentials
and will verify the given token has permissions to access the request resource
- Uses
- From SSO management dashboard select the each of the front end apps
- Assign any scopes you want from the power resource and feel free to assign them all or only a few if you want to see how things fail
this uri is used when users browser is redirected from the sso-hero-web
app to your sso login page. Once the authorization grant code is created sso will redirect the browser back to sso-hero-web
using the /authorization_code
endpoint
- https://sso-hero-web./authorization_callback
the following examples creates user1 and user2
uaac user add --emails user1@domain.com
User name: user1
Password:
Verify password:
user account successfully added
uaac user add --emails user2@domain.com
User name: user2
Password:
Verify password:
user account successfully added
Then we need to set the their scopes
uaac member add power.fly user1
uaac member add power.strength user1
uaac member add power.invisibility user1
uaac member add power.fly user2
uaac member add power.strength user2
uaac member add power.invisibility user2
godeps is used to manage dependencies between both apps. Currently auth
and tracer
packages are organized by godeps. If you plan to make changes to these packages you will have to regenerate the godeps dependency references.
- go get github.com/tools/godep
- rm -rf hero/Godeps hero/vendor web/Godeps web/vendor
- cd hero; godep save;
- cd web; godep save;