Ejemplo de configuración con todas las propiedades posibles, las propiedades que son necesarias revisar siempre son las que se encuentran bajo ‘totplugin' o 'eureka’, el resto solo para instalaciones con una personalización muy avanzada
####################################################################################################
# Example YAML for Tot Plugin LDAP #
# #
# This file has all the technical properties that can be edited for the client. #
# These properties have a default value in the application, #
# so there is no necessity to configure them. #
# Only configure these properties if they are going to be different to the value of this file, #
# this will make your files more clean and readable. #
####################################################################################################
#########################
### Server properties ###
#########################
server:
# Port where service will be listening
port: 15015
#############################
### Tot Plugin properties ###
#############################
totplugin:
server:
# Tot server URL. It is a list because Tot can have more than one instance running.
urls:
- https://tot1server.anjanadata.local/totserver/
connection:
- name: instance-1
aris:
- ari: "anja:totplugin:im:/ldap/ldap/ldap/"
technology:
################################
## LDAP connection properties
## url: where ldap service is running
## base: base LDAP path
## baseUser: base user. If using Active Directory the user must have the full DN (eg. CN=username,CN=Users,DC=dev,DC=local)
## baseGroup: base group
## user: user to log in
## password: password
##
## ldap attributes
##
## userCn: the user common name
## user: user class name used to create users. The default value 'person'
## member: the name of member attribute
## groupCn: the group common name
## group: group class name used to create groups. The default value 'groupOfNames' must have a cn attribute and a member attribute
## groupCaseTransformation: Custom Anjana LDAP property. Transformation applied to group name when physical name does not exist. Possible values: UPPER, LOWER or NONE.
## MANDATORY properties when using an Active Directory like Windows AD
## extraGroupCn: list of attributes to be included with the sme value as groupCn
## extraUserCn: list of attributes to match the user id
## groupParam: under this property can place any property that want to be set into a group int its creation
## ex.: instanceType: 4 to create a Group in Windows AD with the type specified by the Security Department of the Client Company
##
## groupPrefix: the prefix to concat before the dsa object name in ldap
################################
url: url
base: dc=anjanadata,dc=org
baseUser: ou=people
baseGroup: ou=groups
user: uid=admin,ou=system
password: password
attributes:
userCn: cn
user: person
member: member
groupCn: cn
group: groupOfNames
groupCaseTransformation: NONE
extraGroupCn:
- sAMAccountName
extraUserCn:
- mail
groupParam:
instanceType: 4
groupPrefix: Dsa_
#########################
### Logs properties ###
#########################
logging:
pattern:
# Pattern to convert logs in the convenient format for the client
console: "%clr(%d{yyyy-MM-dd HH:mm:ss.SSS}){faint} [TOT-PLUGIN-LDAP] %clr(${LOG_LEVEL_PATTERN:%5p}) %clr(${PID:- }){magenta} %clr(---){faint} %clr([%15.15t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} %m%n${LOG_EXCEPTION_CONVERSION_WORD:%wEx}"
# Mark the level of log to show for every package. ERROR > WARN > INFO > DEBUG > TRACE
level:
# The main log level this is the base for all logs
root: info
# Every package of code can be marked with a different log level, every package of code printed on log is selectable to have a record here and mark a log level
com.anjana: DEBUG
#################################
### Hecate(Eureka) properties ###
#################################
eureka:
client:
serviceUrl:
# Url where Tot is listening
defaultZone: https://tot1server.anjanadata.local/totserver/eureka