1. Anonymous User(Eddie Konczal)
  2. Pre-sale questions
  3. Thursday, 30 July 2020
  4.  Subscribe via email
When I attempt to install RO Single Sign On version 1.2.0, I get these errors:


Warning
JInstaller: :Install: Error SQL Invalid default value for '_expire'
Extension Install: SQL error processing query: DB function failed with error number 1067
Invalid default value for '_expire'
SQL =

CREATE TABLE IF NOT EXISTS `#__saml_LogoutStore`
(
`_authSource` varchar(191) NOT NULL,
`_nameId` varchar(40) NOT NULL,
`_sessionIndex` varchar(50) NOT NULL,
`_expire` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
ON UPDATE CURRENT_TIMESTAMP,
`_sessionId` varchar(50) NOT NULL,
UNIQUE KEY `_authSource` (`_authSource`(191), `_nameId`, `_sessionIndex`),
KEY `#__saml_LogoutStore_expire` (`_expire`),
KEY `#__saml_LogoutStore_nameId` (`_authSource`(191), `_nameId`)
)
ENGINE = InnoDB
DEFAULT CHARSET = utf8;

Package Install: There was an error installing an extension: com_ro_sso_1.2.0.zip


Here is the system configuration:

PHP Built On Linux 4.12.14-197.45-default #1 SMP Thu Jun 4 11:06:04 UTC 2020 (2b6c749) x86_64
Database Type mysql
Database Version 5.5.39
Database Collation utf8_general_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 7.2.5
Web Server Apache
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.10.0-alpha1 Alpha [ Amani ] 23-July-2020 21:10 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

Regards,
Eddie
Accepted Answer Pending Moderation
Hello Eddie,

This is not a support section but a pre-sales section for asking questions about our products. Support is only given if you have an active membership and I don't see an active RO Single Sign On subscription in your name.

Since you don't have an active subscription I wonder how you came by our software. It is open source so no problem there but we cannot support non-members.
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Accepted Answer Pending Moderation
Hi, Roland,



I work with Laura Gordon at Rutgers University. We are testing this extension to see if it will work with Rutgers’ central authentication server. I’m copying
Laura on my reply.



Regards,

Eddie





From: RolandD Cyber Produksi <support@rolandd.com>


Sent: Thursday, July 30, 2020 4:36 PM

To: Edward Konczal <konczal@sas.rutgers.edu>

Subject: [#63545]: Errors installing RO Single Signon (Reply)
Accepted Answer Pending Moderation
Yes, Roland, is there a way we can get support on the installation so we can test this out?

thank you!!!


-- Laura & team (Eddie Konczal, Michelle Martel, Stephen Kujan)
Accepted Answer Pending Moderation
Hello Eddie,

Your post was without context for me hence my reply.

You are running an old MySQL version and I guess that is why it doesn't execute the query. You can manually create the table and see what the value should be for a DATETIME default value. This field does need this default because it is used for automatically setting a timestamp.

If the table already exists this will be skipped during installation, so that should finish then. Unless there are other incompatibilities with the old MySQL version, will find out soon enough when you install.

The other option is to use a more recent version of MySQL but not sure if that is an option.
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Accepted Answer Pending Moderation
Roland,
Hi, I will manually create the table, but more importantly, what version of MySQL do you recommend?

thanks
Laura
Accepted Answer Pending Moderation
I found the issue...

1. We are on mysql 5.5, from mysql:
solution from mysql note:
The DEFAULT CURRENT_TIMESTAMP support for a DATETIME (datatype) was added in MySQL 5.6.
In 5.5 and earlier versions, this applied only to TIMESTAMP (datatype) columns.
It is possible to use a BEFORE INSERT trigger in 5.5 to assign a default value to a column

2. I adjusted the table by trying the code:
CREATE TABLE IF NOT EXISTS `#__saml_LogoutStore`
(
`_authSource` varchar(191) NOT NULL,
`_nameId` varchar(40) NOT NULL,
`_sessionIndex` varchar(50) NOT NULL,
`_expire` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
ON UPDATE CURRENT_TIMESTAMP,
`_sessionId` varchar(50) NOT NULL,
UNIQUE KEY `_authSource` (`_authSource`(191), `_nameId`, `_sessionIndex`),
KEY `#__saml_LogoutStore_expire` (`_expire`),
KEY `#__saml_LogoutStore_nameId` (`_authSource`(191), `_nameId`)
)

this was created successuflly

3. but when the code is running, it still 'crashes, even if the table saml_LogoutStore already exists

To confirm, we need mysql 5.6 to use single signon?

thanks,
Laura
Accepted Answer Pending Moderation
One more question, if we have MariaDB 10.2.31, what version specifically are you working under, I see:

COLUMNS table, a default CURRENT TIMESTAMP is displayed as CURRENT_TIMESTAMP up until MariaDB 10.2. 2, and as current_timestamp() from MariaDB 10.2. 3, due to to MariaDB 10.2 accepting expressions in the DEFAULT clause.
Accepted Answer Pending Moderation
Hello Laura,

Correct MySQL 5.6 is good enough.

but when the code is running, it still 'crashes, even if the table saml_LogoutStore already exists
You get the same exact error? I need more information I am afraid than "it still crashes". It can hardly be the same error if the table already exists.

As for MariaDB, I have no experience with that but generally any version compatible with MySQL 5.6 should work as well.
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Accepted Answer Pending Moderation
Table on site: https://snipboard.io/6Q7K5L.jpg

JInstaller: :Install: Error SQL Invalid default value for '_expire'
Extension Install: SQL error processing query: DB function failed with error number 1067
Invalid default value for '_expire'
SQL =

CREATE TABLE IF NOT EXISTS `#__saml_LogoutStore`
(
`_authSource` varchar(191) NOT NULL,
`_nameId` varchar(40) NOT NULL,
`_sessionIndex` varchar(50) NOT NULL,
`_expire` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
ON UPDATE CURRENT_TIMESTAMP,
`_sessionId` varchar(50) NOT NULL,
UNIQUE KEY `_authSource` (`_authSource`(191), `_nameId`, `_sessionIndex`),
KEY `#__saml_LogoutStore_expire` (`_expire`),
KEY `#__saml_LogoutStore_nameId` (`_authSource`(191), `_nameId`)
)
ENGINE = InnoDB
DEFAULT CHARSET = utf8;

Package Install: There was an error installing an extension: com_ro_sso_1.2.0.zip
Accepted Answer Pending Moderation
Hello Laura,

The only thing I can think of is that the table prefix is incorrect because SQL won't execute the statement if the table already exists. That is why the create statement has the IF NOT EXISTS. Can you double check that the prefix is correct?
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Accepted Answer Pending Moderation
So since this is a 'public' display, I 'scratched' out the 'prefix', but yes, it's using the same prefix as all of our other joomla tables...and it has the same as the Database Tables Prefix in the configuration...

It's interesting that it's still trying to create the table...

I do see the tables:
xxx_sso_clients
xxx_sso_profiles
xxx_saml_LogoutStore

Could it be the 'capital' letters? that is tricking it?

I'm also looking into adjusting our mysql server to be MariaDB10... if we can't get it to work..
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
Laura Gordon
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below. Supports gif,jpg,png,jpeg,zip,rar,pdf,csv,txt,tsv,xml,docx,doc,xls,xlsx,ods,tgz
• Insert • Remove Upload Files (Maximum File Size: 2 MB)
In this section you can provide your site details at here and it visible to the moderators only.