Axpert-11.0.0.0
Axpert-10.9.0.0
- 10.9.1.0 release01
- 10.9.1.0 release02
- 10.9.1.0 release03
- 10.9.1.0 release04
- 10.9.1.0 release05
- 10.9.1.0 release06
- 10.9.1.0 release07
- 10.9.1.0 release08
- 10.9.1.0 release09
- 10.9.1.0 release10
- 10.9.1.0 release11
- 10.9.1.0 release12
- 10.9.1.0 release14
- 10.9.1.0 release15
- 10.9.1.0 release16
- 10.9.1.0 release17
- 10.9.1.0 release18
- 10.9.1.0 release19
- 10.9.1.0 release20
- 10.9.1.0 release21
- 10.9.1.0 release22
- 10.9.1.0 release23
- 10.9.1.0 release24
- 10.9.1.0 release25
- 10.9.1.0 release26
- 10.9.1.0 release27
- 10.9.1.0 release28
- 10.9.1.0 release29
- 10.9.1.0_release30
- 10.9.1.0_release31
- 10.9.1.0_release32
- 10.9.1.0_release33
- 10.9.1.0_release34
Axpert-10.8.0.0
- 10.8.0.0
- 10.8.1.0 release01
- 10.8.1.0 release02
- 10.8.1.0 release03
- 10.8.1.0 release04
- 10.8.1.0 release05
- 10.8.1.0 release06
- 10.8.1.0 release07
- 10.8.1.0 release08
- 10.8.1.0 release09
- 10.8.1.0 release10
- 10.8.1.0 release11
- 10.8.1.0 release12
- 10.8.1.0 release13
- 10.8.1.0 release14
- 10.8.1.0 release15
- 10.8.1.0 release19
- 10.8.1.0 release20
- 10.8.1.0 release21
- 10.8.1.0_release22
Axpert-10.7.0.0
Axpert-10.6.0.0
-
10.6.0.0
-
10.6.0.1 release01
-
10.6.0.1 release02
-
10.6.0.1 release03
-
10.6.0.1 release04
-
10.6.0.1 release05
-
10.6.0.1 release06
-
10.6.0.1 release07
-
10.6.0.1 release08
-
10.6.0.1 release09
-
10.6.0.1 release10
-
10.6.0.1 release11
-
10.6.0.1 release12
-
10.6.0.1 release13
-
10.6.0.1 release14
-
10.6.0.1 release15
-
10.6.0.1 release16
-
10.6.0.1 release17
-
10.6.0.1 release18
The Release Contains below-mentioned Bug Fixes
- Require SSO SAML login option for workflow approval page.
- Unable to trigger email on web . SMTP TLS Upgrade issue(DLL fix).
- SAML SSO Authentication enhanced
Steps to Enable SAML SSO:
Need to add/Enable below web.config keys.
<add key=”SamlPartnerIdP” value=””/>
<add key=”ssologin” value=””/>
<add key=”ssoredirecturl” value=””/>
<add key=”SamlIdentifier” value=””/>
<add key=”SamlCertificate” value=””/>Add this assembly reference in assemblies section
<add assembly=”System.Security, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A”/>
Ex.: <add key=”SamlPartnerIdP” value=”https://login.microsoftonline.com/0b1513a2-8f4d-4478-ab27-28da7a534984/saml2″/>
[After add application in Azure AD portal it will generate ‘Login URL’ that need to be copied ]
<add key=”ssologin” value=”saml”/>
<add key=”ssoredirecturl” value=”http://demo.agile-labs.com/”/>
<add key=”SamlIdentifier” value=””/>
[After add application in Azure AD portal it will have ‘Identifier (Entity ID)’ that need to be add]
<add key=”SamlCertificate” value=””/>
[Download SAML Azure AD application certificate and copy to web code Saml_Certificates folder. Create a text file with the same name as the certificate file and copy content from the certificate file to the text file followed by @ and then add the text file name in SamlCertficate web. config key value]
Note: below open source, dll added for Cryptography.Xml
System.Security.Cryptography.Xml.dll - On Change of params in Ivew, the report is unable to not fetch records as it shows loading.