New-RunAsAccount.ps1 throws exception System.Excpetion about pci-paas-webapp-ase-sqldb-appgateway-keyvault-oms

[ShabuddinKhan]

Hi Bryan @bmacm,

I just tested it and did not received any error.

New-RunAsAccount.ps1 creates a self-signed certificate, set certificate expiry (by default to 12 months) and use it to create a new AD Application. If you are running script manually then make sure you set the expiry correctly.

**"date": "2017-07-11T12:57:05",**
"requestId": "09fb8874-****-****-****00d5698e82ec",

If the above highlighted date is 'end date' then it might be possible that key credential was using same date as start and end date. Also, I see that you have mentioned - "Between Friday 7th and Monday 11th July". Does that mean you were able to run it before 7th July and after 11th July ? Are you still getting the same error ?

[bmacm]

Hi Shabuddin thanks for getting back,

Sorry I should have been more clear. On Friday the 7th everything was working as you describe above, from Monday 11th July onward I am getting the below error.

Adding the -debug flag at the end of the New-AzureRmADApplication command on line 60 of New-RunAsAccount.ps1 gives this output from step 7

We are using the self-signed certificate method, and I have checked the generated certificate has a valid end date which seems to be correct assigned in line 54-55 of the RunAsAccount.ps1 file.

We are using powershell verions

We also updated to yesterdays Azure Modules 4.2.0 release but this does not seem to have made any difference.

[bmacm]

Hi @ShabuddinKhan

We have found the issue, my colleague will submit a pull request shortly. The issue seems to be how the scripts are picking up the End Date of the self-signed certification on line 54 of New-RunAsAccount.Ps1 The way in which this script parses to date time via [DateTime] does not take care of localised datetime on a developers PC. Updating this to use the Get-Date function will deal with locals.

As Friday was the 7th of July i.e 7/7/17 this was not a issue, but from Saturday the 8th the confusion between US and UK date format caused this issue (7/8/17 is the 7th of Aug in the UK, it should be 8/7/17 the 8th of July).

Thanks again, and awesome work on this solution - you guys are saving us weeks of scripting effort :-) This is an excellent base sample/POC project for us to start our own efforts.

[ShabuddinKhan]

Hi @bmacm
Yes, I see the difference. Good to know that you have managed to fix the issue. Do submit a pull request so we can test it at our end too.
Cheers!