Hi Inosh, I doubt we need to do it since as we know IS will be having CA and SCEP integration into next IS release most probably. So what we are looking at is to integrate that support. My personally belief is that these should not go under EMM hence on IS. This is something we need to think about by looking at IS deliverable. Anyway auto creation of BKS to Android etc. could come under our scope.
Please find my comments inline. > > - Need to write a carbon component, instead of the using a > JAR(currently it is using a JAR), for Jaggery backend to communicate. > > +1. Bouncycastle has been added into EMM project recently. You can make use of that. > > - There are conflicts in the bouncy castle library used in the wizard > project and when installing the Apk on some version of android OS. Since > android is packed with a bouncy castle version, a bks created with a > different version can cause this issue. Need to look into including spongy > castle library to avoid this issue. > > Yes I think you have to look into SpongyCastle for this. > > - Add authentication to the Jaggery app, so that only the admin user > can create JKS and Apk files. > > How should the authentication needs to be done for this app? Since it > is not implemented at all currently. > > > Same SSO approach. -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
