search

UniTime / unitime

Comprehensive University Timetabling System
http://www.unitime.org
Apache License 2.0
282 stars 162 forks source link

Wrong authorization - UniTime Glassfish #31

Closed marcosaguileraely closed 6 years ago

marcosaguileraely commented 6 years ago

I've deployed UniTime 4.0 in my Glassfish Server successfully, and the timetable blank-data.sql database in my Mysql db engine.

According with the documentation everything is working on the server, but when I've tried to login to UniTime, login windows say:

http://myserver:8080/UniTime/login.do User: admin Pass: admin (according with the documentation)

Authentication failed: Login Failure: all modules ignored.

PDT: My mysql database and Glassfish are not in the same server (both in diff servers), I've just edit the hibernate.cfg.xml into timetable.jar. 


<!-- MySQL Configuration -->
    <property name="connection.driver_class">com.mysql.jdbc.Driver</property>
    <property name="connection.url">jdbc:mysql://x.x.x.x:3306/timetable</property>
    <property name="connection.username">mydbuser</property>
    <property name="connection.password">mypass</property>
    <property name="connection.autocommit">true</property>
    <property name="dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>
    <property name="tmtbl.uniqueid.generator">org.hibernate.id.TableHiLoGenerator</property>
    <property name="hibernate.connection.useUnicode">true</property>
    <property name="hibernate.connection.characterEncoding">utf8</property>
    <!-- End of MySQL Configuration -->

Glassfish took the changes and not says errors or warnings.

May be it causes the issue?
Could you guys help me with this authentication issue?

Thanks a lot.
tomas-muller commented 6 years ago

First of all, you do not need to edit hibernate.cfg.xml. The database connection properties can be provided in the custom properties file, see http://help.unitime.org/Timetabling_Installation#TOC-Customization for more details.

Are there any errors in the logs? Can you verify that UniTime is able to connect to the database? Ideally, you should see something like this in there:

[10/07/17 04:02:08] INFO   afterPropertiesSet ->  - Initializing Hibernate ... 
[10/07/17 04:02:08] INFO   Version -> HCANN000001: Hibernate Commons Annotations {4.0.5.Final}
[10/07/17 04:02:08] INFO   Version -> HHH000412: Hibernate Core {4.3.11.Final}
[10/07/17 04:02:09] INFO   ConnectionProviderInitiator -> HHH000130: Instantiating explicit connection provider: org.unitime.commons.hibernate.connection.LoggingDBCPConnectionProvider
[10/07/17 04:02:10] INFO   LoggingDBCPConnectionProvider -> Database connection pool logging is enabled.
[10/07/17 04:02:10] INFO   Dialect -> HHH000400: Using dialect: org.hibernate.dialect.MySQLInnoDBDialect
[10/07/17 04:02:10] INFO   ASTQueryTranslatorFactory -> HHH000397: Using ASTQueryTranslatorFactory
[10/07/17 04:02:13] INFO   UpdateTimestampsCache -> HHH000250: Starting update timestamps cache at region: org.hibernate.cache.spi.UpdateTimestampsCache
[10/07/17 04:02:13] INFO   StandardQueryCache -> HHH000248: Starting query cache at region: org.hibernate.cache.internal.StandardQueryCache
[10/07/17 04:02:14] INFO   run -> InfoCache cleanup thread started.
[10/07/17 04:02:19] INFO   SessionFactoryRegistry -> HHH000094: Bound factory to JNDI name: unitime:hibernate/SessionFactory
[10/07/17 04:02:19] INFO   TransactionFactoryInitiator -> HHH000399: Using default transaction strategy (direct JDBC transactions)
[10/07/17 04:02:20] INFO   <init> -> Reading file:/usr/local/apache-tomcat-7.0.39/webapps/UniTime/WEB-INF/lib/timetable.jar!/dbupdate.xml ...
[10/07/17 04:02:20] INFO   DatabaseUpdate -> Current UniTime database version: 123
[10/07/17 04:02:20] INFO   DatabaseUpdate ->   Performing UniTime update to version 124 (Instructor Note)
[10/07/17 04:02:20] INFO   DatabaseUpdate ->     UniTime Database version increased to: 124
...
[10/07/17 04:03:26] INFO   DatabaseUpdate ->   Performing UniTime update to version 189 (Larger Event Note)
[10/07/17 04:03:34] INFO   DatabaseUpdate ->     UniTime Database version increased to: 189
[10/07/17 04:03:35] INFO   DatabaseUpdate -> New UniTime database version: 189
[10/07/17 04:03:35] INFO   afterPropertiesSet ->  - Creating Message Log Appender ... 
[10/07/17 04:03:35] INFO   afterPropertiesSet ->  - Initializing Room Availability Service ... 
[10/07/17 04:03:35] INFO   afterPropertiesSet ->  - Cleaning Logs ...
[10/07/17 04:03:35] INFO   LogCleaner -> All records older than 14 days deleted from the student sectioning queue (9 records).
[10/07/17 04:03:40] INFO   afterPropertiesSet ->  - Starting Event Expiration Service ...
[10/07/17 04:03:40] INFO   EventExpirationService -> Event expiration service started.
[10/07/17 04:03:40] INFO   afterPropertiesSet -> ******* UniTime 4.2.185 build on Sat, 7 Oct 2017 initialized successfully *******