server.ssl.key-store=file:/etc/cas/thekeystore
server.ssl.key-store-password=changeit
logging.config=file:/etc/cas/config/log4j2.xml
cas.service-registry.core.init-from-json=true
cas.serviceRegistry.json.location=file:/etc/cas/services
logging.level.org.apache.commons.logging=DEBUG
cas.authn.accept.users=
# Specify MySQL driver class
cas.authn.jdbc.query[0].driver-class=com.mysql.cj.jdbc.Driver
# Modify the JDBC URL to connect to your MySQL database
cas.authn.jdbc.query[0].url=jdbc:mysql://localhost:3306/bitlabs
# Specify MySQL dialect
cas.authn.jdbc.query[0].dialect=org.hibernate.dialect.MySQL57Dialect
# Specify MySQL database credentials (username and password)
cas.authn.jdbc.query[0].user=root
cas.authn.jdbc.query[0].password=
# Adjust SQL query to match MySQL syntax and table name
cas.authn.jdbc.query[0].sql=SELECT * FROM mdl_user WHERE email = ?
# Specify the password encoder type (assuming BCRYPT is still used)
cas.authn.jdbc.query[0].password-encoder.type=BCRYPT
# Specify the field names for password, expired, and disabled columns in your MySQL table
cas.authn.jdbc.query[0].field-password=password
cas.authn.jdbc.query[0].field-expired=expired
cas.authn.jdbc.query[0].field-disabled=disabled
I am facing 2 issues:
Application Not Authorized to Use CASThe application you attempted to authenticate to is not authorized to use CAS. This usually indicates that the application is not registered with CAS, or its authorization policy defined in its registration record prevents it from leveraging CAS functionality, or it's malformed and unrecognized by CAS. Contact your CAS administrator to learn how you might register and integrate your application with CAS.
Issue 2: