Applications are sometimes faced with a complicated login schema to authenticate different user profiles. For example, one profile authenticates with Microsoft ADFS, another with the internal Betty Blocks authentication or username & password. You want to manage and simply apply these different profiles in your application. Therefore we made this new feature called authentication profiles. Here is what we have done:
Your webuser definition in My Betty Blocks (Settings > Login) is migrated to the new authentication profiles. This has only been done, if a webuser definition was created. The name of this profile is Username/Password by default. We migrated the password's ShaBit length setting to the password property itself, because that setting belongs to that property type. Check out this learn article for more information about what authentication profiles are.
How do I apply authentication profiles? You can use a profile to authenticate web pages with. If your page requires authentication, you have to select which profile users (who enters your page) have to authenticate themselves with. For example your customer portal requires authentication with a username and password profile. In this profile, you have selected a redirect page in case a user isn't logged or the user's session is expired. Users are probably redirected to a login screen. The action which processes the login flow contains a login action event. We have slightly changed this action event too. It now requires a profile to authenticate and to login or logout. We also changed the name of the event into 'authenticate and login user' to be more clear what it does. Please read this learn article for more information about how to apply authentication profiles.
