# WorkflowGen 7.11.0 **URL:** \ **Category:** Release Notes & Downloads\ **Created:** [June 15, 2018, 2:02pm UTC](https://discuss.workflowgen.com/t/workflowgen-7-11-0/1072 "2018-06-15T14:02:50Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\ **Post date:** [June 15, 2018, 2:02pm UTC](https://discuss.workflowgen.com/t/workflowgen-7-11-0/1072/1 "2018-06-15T14:02:50Z")
## Official release (June 18, 2018) ### Important known issues - We have recently identified a regression bug ([#2073](https://discuss.workflowgen.com/t/workflowgen-7-14-1)) in this release that could affect the directory synchronization service with the Active Directory and LDAP connectors when the directory uses a login configured with AES (FIPS compliant) or Version 5 (Legacy) password management mode with an Encryption key. - [WorkflowGen OpenID Connect authentication configuration issue.](https://discuss.workflowgen.com/t/known-issue-workflowgen-openid-connect-authentication-configuration-issue) ### General - Feature (#1572, #1713): Supports new `Azure AD (v1 endpoint)`, `Auth0`, and `ADFS` authentication methods with the OpenID Connect standard. See the [WorkflowGen Technical Guide](https://advantys.gitbooks.io/workflowgen-technical-reference-guide/content/) for information on how to configure each authentication method. - Bug (#1657): The WorkflowGen HTTP authentication for applicative and OpenID methods now always writes log files in the WorkflowGen `app_data\logfiles` folder. ### Administration - Feature (#1420): Added a new `Azure AD SCIM v2` type directory connector to support Azure Active Directory synchronization with the SCIM web API. ### Workflow Applications - Feature (#1608): Added a new `Non interactive client` application type to allow non interactive clients (e.g. daemon) to access the GraphQL web API based on the chosen OpenID Connect authentication mode. ### Configuration panel - Feature (#1572, #1713): Added new `Azure v1`, `Auth0`, and `ADFS` authentication modes. See the [WorkflowGen Technical Guide](https://advantys.gitbooks.io/workflowgen-technical-reference-guide/content/) for information on how to configure each authentication method. - Change (#1647): Removed the legacy `Session` authentication mode. ### GraphQL v1.0.0-beta.5 - Version update from `1.0.0-beta.4` to `1.0.0-beta.5` - Performance (#1754): The default iisnode `nodeProcessCountPerApplication` configuration is now set to create the same number of node processes as the number of virtual CPU cores on the server. - Enhancement (#1288): Added new `synchronizationConnector` field to the `directory` type. - Enhancement (#1289): Added new `synchronizationConnector` filter to `directories`. - Enhancement (#1739): Added a new `maxRequestBodySize` configuration parameter to set the default request body size limit. - Bug (#1683): Fixed an `Object reference` exception error when a user completes an action for which they were not authorized. - Bug (#1691, #1722): Fixed an issue where an incorrect error message would be returned when a user accessed a non-existing request or action. - Bug (#1728): Fixed an issue where a file upload with `base64string` content was limited to 100 kB. - Bug (#1753): Fixed an issue where it was possible for administrators to delete a sub-request. ### Webhooks v3.2.0 - Version update from `3.1.1` to `3.2.0` - Performance (#1754): The default iisnode `nodeProcessCountPerApplication` configuration is now set to create the same number of node processes as the number of virtual CPU cores on the server. - Enhancement (#1738): Added a new `maxRequestBodySize` configuration parameter to set the default request body size limit. - Bug (#1683): Fixed an `Object reference` exception error when a user completes an action for which they were not authorized. - Bugs (#1691, #1722): Fixed an issue where an incorrect error message would be returned when a user accessed a non-existing request or action. - Bug (#1725): Fixed an issue where a file upload with `base64string` content was limited to 100 kB. - Bug (#1753): Fixed an issue where it was possible for administrators to delete a sub-request. ### Auth v1.0.0-beta.1 - Feature (#1702): New web API module to handle OpenID Connect authentication with Azure, Auth0, or ADFS. ### SCIM v1.0.0-beta.1 - Feature (#1285): New web API module to handle Azure Active Directory synchronization based on the SCIM v2 specification. ### Database - Enhancement (#1620): Added support for Azure SQL database. ### Notes - All of the above Node.js modules (`GraphQL v1.0.0-beta.5`, `Webhooks v3.2.0`, `Auth v1.0.0-beta.1`, and `SCIM v1.0.0-beta.1`) now require **Node.js version `8.11.3`**. - Running the `npm install --production` command is required on each of the modules (`\wfgen\graphql`, `\wfgen\hooks`, `\wfgen\auth`, and `\wfgen\scim`) after the upgrade. ### Reminders - **Microsoft Windows Server 2008 is no longer supported as of WorkflowGen version 7.11.0.** We recommend migrating to Windows Server 2012 or later. - **Microsoft SQL Server 2008 is no longer supported as of WorkflowGen version 7.10.0.** While SQL Server 2008 is still compatible with WorkflowGen, support for any performance issues or bugs resulting from using SQL Server 2008 will no longer be provided. ### Installation packs [WorkflowGen 7.11.0 (Upgrade)](http://download.workflowgen.com/product/7-11-0/update.zip) [WorkflowGen 7.11.0 (Clean install - PowerShell)](http://download.workflowgen.com/product/7-11-0/powershell-setup-7-11-0.zip) [WorkflowGen 7.11.0 (Clean install - manual)](http://download.workflowgen.com/product/7-11-0/manual.zip) [WorkflowGen.My 4.2.0](http://download.workflowgen.com/library/wfg-my/4-2-0/wfg-my.zip) ### Docker image [WorkflowGen Docker image](https://hub.docker.com/r/advantys/) ### Documentation [WorkflowGen 7.11.0 Upgrade Guide](https://advantys.gitbooks.io/workflowgen-upgrade-guide/content/) [WorkflowGen 7.11.0 Technical Guide](https://advantys.gitbooks.io/workflowgen-technical-reference-guide/content/) [WorkflowGen 7.11.0 Administration Guide](https://advantys.gitbooks.io/workflowgen-administration-module-reference-guide/content/) [WorkflowGen 7.11.0 User Portal Guide](https://advantys.gitbooks.io/workflowgen-user-portal-reference-guide/content/) [WorkflowGen Integration Guide](https://advantys.gitbooks.io/workflowgen-integration-guide/content/) ---
**Author:** ![pnicoll](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/pnicoll/32/454_2.png) [@pnicoll](https://discuss.workflowgen.com/u/pnicoll)\ **Post date:** [June 18, 2018, 6:14pm UTC](https://discuss.workflowgen.com/t/workflowgen-7-11-0/1072/2 "2018-06-18T18:14:40Z")
---
**Author:** ![pnicoll](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/pnicoll/32/454_2.png) [@pnicoll](https://discuss.workflowgen.com/u/pnicoll)\ **Post date:** [July 13, 2018, 8:56pm UTC](https://discuss.workflowgen.com/t/workflowgen-7-11-0/1072/3 "2018-07-13T20:56:48Z")
---
**Author:** ![kevin.lee](https://avatars.discourse-cdn.com/v4/letter/k/65b543/32.png) [@kevin.lee](https://discuss.workflowgen.com/u/kevin.lee)\ **Post date:** [July 20, 2018, 2:31pm UTC](https://discuss.workflowgen.com/t/workflowgen-7-11-0/1072/4 "2018-07-20T14:31:46Z")
Hi, It mentions that Node.js version 8.11.3. is required. What happen if there are multiple instances of WFGEN installed and some of them are running the older version which require Node.js v6? ---
**Author:** ![eddy.daouk](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/eddy.daouk/32/672_2.png) [@eddy.daouk](https://discuss.workflowgen.com/u/eddy.daouk)\ **Post date:** [July 24, 2018, 10:22pm UTC](https://discuss.workflowgen.com/t/workflowgen-7-11-0/1072/5 "2018-07-24T22:22:33Z")
Hi Kevin, You can only run a single active version of Node on the WorflowGen production server. If there are multiple instances of WFG on the same server then these instances must support the same active version of Node.js On the other hand, if this is a development environment (test or develop on different version of WFG) then it can use nvm-windows ([https://github.com/coreybutler/nvm-windows](https://github.com/coreybutler/nvm-windows)) to handle the Node versions on the same machine. But it is the same scenario; one active version at a time. Regards, Eddy.