Re: [keycloak-dev] 1.0 Final roadmap

See comments in-line Mobile adapters would be really good to have. If we can get help from the AeroGear team to do these, maybe we could include this as well? For simplicity we could just aim for a working Cordova example, but Android and iOS adapters would be great. It would also be nice to make Keycloak more "embeddable". I'd like to be able to improve how Keycloak is embedded into LiveOak, but there's also the issue around WildFly console needing to embed it. Let's have a separate thread on this, but my current (updated) thinking is to utilize RestEasy, but to remove use of servlets There's a whole bunch of JIRA issues with fix for beta1. In the effort to prune this list a bit, here's some I think we can postpone to later: KEYCLOAK-313 Manage devices KEYCLOAK-311 Custom user profiles KEYCLOAK-310 SPI for multi-factor authentication KEYCLOAK-308 Cordova adapter KEYCLOAK-307 iPhone adapter KEYCLOAK-306 Android adapter KEYCLOAK-301 Internationalization support KEYCLOAK-300 Auto configuration of MySQL or PostgreSQL in OpenShift cartridge KEYCLOAK-266 Integrated help in admin console KEYCLOAK-265 Optional instructions to social providers KEYCLOAK-242 Add remember machine option for two factor authentication KEYCLOAK-182 List applications on account management KEYCLOAK-161 Allow users to create oauth clients through account pages KEYCLOAK-57 Mobile example application ----- Original Message ----- Any particular reason for June? We probably need a separate thread to discuss this, but it's important that users can view what applications can currently access their account and revoke access to individual apps. This means we need to know what refresh tokens are valid, and which have been revoked by a user. Is this really required for the first release? Related things we'll need are brute force protection (including max failed login attempt before locking a users account) and email notifications on certain events.