we're currently developing several zimlets that integrate with other systems (eg. cms, erp, etc).
These zimlets (more precisely: their backend jsp code) need the proper user credentials to these
For now, we're storing them in the user-zimlet-properties, but they can be accessed by frontend
datasource. Options are:
a) filesystem: a bit tricky to guarantee atomicity and not suited for multiserver (would require additional sychronization)
b) mailboxd database: not suited for multiserver, like w/ filesystem
c) ldap: requires schema extension (that must be maintained across zcs separate versions, more complex on zcs upgrades)
d) separate database server: quite complex to set up (far out of scope for a simple zimlet)
The first step we're probably going is to abstract away the access to such information, so we can choose the underlying actual storage later (maybe configurable or even supporting multiple ones).
Any ideas on this ?
- Zimbra Collaboration 9.0.0 now available. Read the release notes.
- Zimbra Collaboration 8.8.15 LTS now available. Read the release notes.
- Are you a Zimbra Developer? You can find some interesting stuff in our Official GitHub, Blog and the Community Github.
- Zimbra is Open Source! Read the FAQ. You can also contribute and build binary from source!
Have a great idea for extending Zimbra? Share ideas, ask questions, contribute, and get feedback.
2 posts • Page 1 of 1
Not a direct answer to your question, but you can use the zimbraZimletDataSensitiveInMixedModeDisabled ldap attr to disable zimlets exchanging sensitive data with the server operating in mixed (both http/https) mode.
Who is online
Users browsing this forum: No registered users and 2 guests