Steaming along

After years of intending to go, I finally visited Richmond Vale Railway Museum yesterday. On the short trip on the steam train I was standing at the rear door of the passenger carriage. It was the the perfect position to take a time lapse video of the return journey as the steam engine pushed the carriage back up the hill.

Tacky

My ride to work this morning was aborted by this little tack that I picked up while riding on the bike path alongside Ford Oval in New Lambton. I hope this is just a random bit of debris and not some idiot deliberately having a go at cyclists.

Salesforce Summer ’19 issue with ADFS single sign on

This is a work related techie blog post for the benefit of others who may experience the same problem.

We have a production Salesforce Org and a number of sandbox Orgs, all set up with a Salesforce “My Domain” and configured to use Single Sign On authenticating against Microsoft ADFS. On the weekend, after our sandbox Orgs got upgraded to the Summer ’19 release, we were unable to login to any of our sandboxes using Single Sign On. We were just getting a very unhelpful “An error occurred” message on the sign-in screen.

Comparing the Single Sign On settings in our Production Org (which was still working), I noticed that where the “Login URL” SAML endpoint used to have an “so=OrgID” parameter, this was now gone in the updated sandboxes. Jumping on to our ADFS management console, and editing the relevant Relying Party Trust to remove the “so=OrgID” parameter from the Endpoint was all that was needed to fix the problem.

Curiously, when I checked the release notes for the Summer ’19 update (which is 480 pages long!), there appears to be no mention of this change in Single Sign In configuration.

Production (not yet updated to Summer ’19) had an “so=” parameter in the Login URL SAML endpoint
Sandboxes that had been updated to Summer ’19 release did not have the “so=” parameter in the Login URL SAML endpoint
Removing the “so=OrgID” parameter in the ADFS settings fixed the sign in problem.

Lizotte’s building

My article for the May 2019 edition of The Local is out. This month I clear up two errors that have appeared in a number of history books regarding the Coronation Hall (now Lizotte’s) in Morehead Street Lambton.

Error The truth
The Coronation Hall was built in 1910, the year George V became king. The Coronation Hall was built in 1911, the year of the coronation of King George V.
The Coronation Hall was built on the site of the Criterion Skating Rink/Star Theatre.

The Criterion Skating Rink was built on the south-west corner of Morehead and De Vitre Streets in 1888. In 1892 it became the Star Theatre.

The Coronation Hall was built on the corner of Morehead and Kendall Streets.

Lambton Council Update

I have just finished making quite a few updates and additions to my Lambton Council Chambers page. In light of Newcastle Council’s impending and controversial move of their council chambers to Newcastle West, I was quite amused by a quote from Alderman Dent in March 1887 in connection with the need for a new Council Chambers for Lambton …

“The present building was a beastly place. When they looked around they saw the very walls in mourning, whether for the sins of the aldermen he knew not.”

Alderman Dent’s desire for new chambers was fulfilled just a few months later when the Council building in the corner of Lambton Park was formally opened on 21 July 1887.

Lambton Council Chambers, September 1890.

True Identity

My April article for The Local is now out, this month on how I uncovered the true identity of one of the men whose name is engraved on the Lambton Park WW1 memorial gates. Private George Sturey was killed in France in 1918, but that wasn’t his real name.

In five years of researching and writing local history, this has been one of the most satisfying discoveries for me. This coming Anzac Day will be an opportunity to remember “George” and his sacrifice with greater clarity, know that we know who he was.