Possible to cascade Force Secure SSL Settings?

(Amurray) #1

Hi Everyone,

 

Is it possible to cascade chosen force secure settings down to all the child assets underneath?

(Admin > Settings Screen > SSL > dropdown)

A script?

 

One by one is going to be a large upcoming task, and just wanting to see your thoughts,

Am currently on Squiz Matrix v4.18.0.

 

 

Cheers!

(Aleks Bochniak) #2

You could use a trigger to do this.

 

Events: Asset Lookups Updated

Conditions: Tree Location: parent root node

Action: Set Force Secure: HTTPS

 

And then do an update lookups on your parent root node.

#3

Hey Aleks thanks for this!  It would be a nice feature to be able to cascade the status. One for the roadmap guys ;)

 

another thing  that is a to do which may save this time is making sure in the system config that anything with the login design attached  has https forced. It can be applied for urls defined on the system config.

 

This hopefully will be a nice neat way to force - without having to rerun triggers - or set up multiple triggers

The system config one was new to me!

(Aleks Bochniak) #4

Remember to check that your design works under https as well, otherwise you will have browser issues.

#5

Remember to check that your design works under https as well, otherwise you will have browser issues.

Thanks Aleks for this tip. We do have https applied to our main designs folder so hopfully this will be ok. - eeik - hopefully!. Knowing our luck something will be missed due to different ways of implementing sites in our CMS. Of course to be tested on QA enviroment

(Amurray) #6

Thank you everyone for your replies - very much appreciated :)

(Micky Gough) #7

This is an ideal situation to use the batch trigger feature. There’s documentation on the manuals website:http://manuals.matrix.squizsuite.net/triggers/chapters/batching

#8

This is an ideal situation to use the batch trigger feature. There's documentation on the manuals website:http://manuals.matrix.squizsuite.net/triggers/chapters/batching

Thanks very much for this Micky! this will indeed help all the current assets. Most of the assets that don't have public read are behind a matrix Login design. We are finding that we also need to  make this change in the system config to make sure that anything via login gets forced via https

 

Wouldn't this setting ideally do the same thing in the system config? - that is changing all the assets without public read to https? or it wouldn't necessarily need to change all the assets to force secure behind logins as the  forced https for login session will just choose the secure url?

 

We do have public assets that we need to serve by https but the large amount we are concerned with are behind a matrix login with our LDAP groups applied.