ibm mobilefirst - Worklight authentication: multiple realms -


want check approach reasonable. @ first sight seems work.

scenario have different classes of users, when validating credentials can determine class. plan have "master" realm manages authentication , subsidiary realms use control access particular adapter procedures, example "gold".

we can protect procedureordinary() realm master , procedurespecial() realm gold.

in master authenticating code (derived doublestepadapter example) can write

wl.server.setactiveuser("master", useridentity); if ( criteria met )      wl.server.setactiveuser("gold", useridentity); 

we never set challenge handler gold realm, authentication realm handled via master realm.

any issues idea.

technically - work. big assumption here user never try access procedure protected "gold" realm before authenticating. overcome problem i'd recommend following approach - need define login-function , logout-function each realm. make sure of login-functions return same json piece (or use same login-function in realms). way doesn't matter realm triggered authentication - same piece of json challenge , app knows how process it.


Comments

Popular posts from this blog

user interface - Python attempting to create a simple gui, getting "AttributeError: 'MainMenu' object has no attribute 'intro_screen'" -

jquery - Common JavaScript snippet to share files on Google Drive, Dropbox, Box.net or SkyDrive -

Android Gson.fromJson error -