Obviously, the goal would be to have some sort of a common authentication between ESME and OFBiz. In the basic use case, all you really need are two users - anonymous and administartor. Anomyous would be for those users who are not administrators. Since I'm assuming that chat would be available for all users, this would mean that users would see the conversations between other users and the administrators. This would also mean that all users could participate in such conversations. In future iterations of the OfBiz / ESME collaboration, other options would be available. Iterations- Use ESME as a separate component
- Make ESME an OFBiz component
QuestionsUser authentication: Currently, ESME has its own authentication user administration and can't use the user administration from the container. We are looking at various means to overcome this gap but we haven't had time to implement them yet. This means that initially there would be a double administration of users. Adding, deleting users and changing user properties would have to occur twice - once in ESME and once in OfBiz. One way to get around this would be to expand our API to deal with such administrative tasks. Since our APis are based on tokens, you would need to store a token in the user object in OFBiz that could later be used when making calls to ESME. |