Additional methods in IdentitySession since 5.4

[limcheekin]

Hi there,

Along the way I implement the Activiti and Spring Security Integration, I find out that the following additional methods added to IdentitySession interface in Activiti 5.4:

   void deleteUserInfoByUserIdAndKey(String userId, String key) {
      throw new UnsupportedOperationException()
   }
   
   void deleteIdentityInfo(IdentityInfoEntity identityInfo) {
      throw new UnsupportedOperationException()
   }
   
   IdentityInfoEntity findUserAccountByUserIdAndKey(String userId, String userPassword, String key) {
      throw new UnsupportedOperationException()
   }
   
   void setUserInfo(String userId, String userPassword, String type, String key, String value, String accountPassword, Map<String, String> accountDetails) {
      throw new UnsupportedOperationException()
   }
   
   byte[] encryptPassword(String accountPassword, String userPassword) {
      throw new UnsupportedOperationException()
   }
   
   String decryptPassword(byte[] storedPassword, String userPassword) {
      throw new UnsupportedOperationException()
   }
   
   IdentityInfoEntity findUserInfoByUserIdAndKey(String userId, String key) {
      throw new UnsupportedOperationException()
   }
   
   List<String> findUserInfoKeysByUserIdAndType(String userId, String type) {
      throw new UnsupportedOperationException()
   }
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

You see all methods above throwing UnsupportedOperationException, it was how it implemented in Activiti Spring Security Integration plugin at the moment as I not sure the purpose/intention of these additional methods, can any Activiti developer tell me what these methods for?

Thanks in advance.

Best regards,
Chee Kin

[jbarrez]

These methods are mainly because we are currently building out the new Explorer UI, like

- storing random user information
- storing user accounts (gmail account, alfresco account)
- storing password encrypted in database.

But I agree with you, these methods do nt need to be implemented by spring security, so throwing an unsupported exception is perfect.

[limcheekin]

These methods are mainly because we are currently building out the new Explorer UI, like

- storing random user information
- storing user accounts (gmail account, alfresco account)
- storing password encrypted in database.

But I agree with you, these methods do nt need to be implemented by spring security, so throwing an unsupported exception is perfect.

Hi Joram,

Thanks for information and agreed on my approach.

Best regards,
Chee Kin