Architect Consultant blog

Introduction The last week we had to implement some Authorization functionality on Cordys BOP4 (CU9) services. During this journey I discovered that there were several ways in defining the security and this makes it very complex (if you’re a first user just like me). So this blog item describes some ways to define the security and my experiences. Ways to Identify Cordys supports several ways to identify users: No identification is used, in this case this is mapped to an “anonymous” authenticated user within Cordys. Cordys. The credentials are put in the soap header request and are mapped to a Cordys user. WS-Security SAML. This can be used for single-sign-on WS-Security User name token. The user puts its identity (user and password, clear text or encrypted are possible) within the soap header This blog item uses the last with clear text user and password. You can set Cordys identification within the LDAP Explorer: Open LDAP Explorer Goto Organization (HRM) > soap nodes ...