The UI Router integration now accepts a forbiddenState option, this is the
state we will send the user to if they are unauthorized for a given state.
This is useful if you want to show a default "Forbidden" view in these
situations.
Added documentation for the $stateChangeUnauthenticated and $stateChangeUnauthorized events!
The ifUserInGroup and ifUserNotInGroup directives now requires you to pass
either a string expression or a reference to a scope variable. I.E. this will
now throw a parse exception unless admin is a reference to a scope property:
<div if-user-in-group="admin">Hello, Administrator</div>It should be re-written to be a string expression with quotes:
<div if-user-in-group="'admin'">Hello, Administrator</div>The ifUserInGroup and ifUserNotInGroup directives now support regular expressions :)
See the documentation of ifUserInGroup for more information
-
The
logoutdirective is renamed tospLogout -
The registration form now uses property names of
givenNameandsurname, instead offirstNameandlastName -
Form submissions now use
application/x-www-form-urlencodedas the Content Type. Your server needs to negotiate this type, if you are using our server SDKs this happens for you. If you wish to continue usingapplication/jsonas the Content Type you can defineSTORMPATH_CONFIG.FORM_CONTENT_TYPE='application/json'in a config block
whileResolvingUseris deprecatead. UseifUserStateKnowninstead.
-
Custom Data on Registration. You can now pass custom data during registration, simply reference
formModel.customData.myCustomPropertyin yourng-modeldirective. This is only possible if you are supplying a custom template to the directive. See thespRegistrationFormdirective for more detail. -
Group-Based Access Control. This can now control access to UI Routes, based on group membership. See
SpStateConfigfor examples. We've also introduced theifUserInGroupandifUserNotInGroupdirectives.
whileResolvingUserwould break after logout (user state was not properly reflected after logout)