Changes that require modification of configuration and administrative settings




Functionality After Before Result of changes
Internet-enabled functionality.
The NSSSecureConnection object and NSS certificates are no longer available for use in 1C:Enterprise script. 1C:Enterprise supported NSS certificates in 8.3.6 compatibility mode. Support of NSS certificates is discontinued.
Internet-enabled functionality.
Support of TLS protocol versions 1.1 and 1.2 is implemented for scenarios where the client certificate is not specified in the connection settings. The SSL protocol version 3.0 is only used when the client application is started with /HttpsForceSSLv3 command-line option. In all other scenarios SSL version 3.0 is not used.

1C:Enterprise ignores the AllowSSLv3 parameter in conf.cfg file.

The InternetMail object does not support SSL version 3.0.

1C:Enterprise only supported TLS protocol version 1.0.

The AllowSSLv3 parameter was available for use in conf.cfg file.

The InternetMail object supported SSL version 3.0.

Increased security of connections established by client applications for Internet operations.
Internet-enabled functionality.
The platform no longer uses cacert.pem file for creating HTTPS/FTPS connections.

The platform uses the root certificate store of the operating system for creating HTTPS/FTPS connections.

This change is not implemented in 8.3.7 compatibility mode.

The platform used cacert.pem file for creating HTTPS/FTPS connections in scenarios where no certificate stores were specified explicitly. The outdated technology is no longer supported.
Managed forms.
For managed forms, the option to update data presentations only for the specified set of form items is implemented. For the RefreshDataRepresentation() method, the UpdateItems parameter is implemented. For the EditTextUpdate system enumeration, the Always value is implemented. The option to specify a set of form items when updating data presentations using the RefreshDataRepresentation() method was not available. Form data can be updated in idle handlers without losing the text being edited in a text box.
Dumping/loading configurations to files.
The dump of the Source property of the FormItemAddition object to a file is more human-readable.

You can restore configuration from files having both property dump formats.

The dump of the Source property of the FormItemAddition object to a file was less human-readable. Dumping configurations to files produces files that are more human-readable.
XML and XDTO support.
Development tools.
Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) is much more detailed.

During the creation of WSDefinitions object, exceptions are raised if the used WSDL description has errors.

The WSDL description used to create WSDefinitions or WSReference objects must comply with the following rules:

  • Its first tag is <definitions>.
  • It includes the targetNamespace attribute of the <xs:schema> element.
  • If it does not comply with the rules, an exception is raised.

This change is not implemented in 8.3.7 compatibility mode.

Error diagnostics for the creation of WS references (both in Designer and using the WSDefinitions object) was not sufficiently detailed.

During the creation of WSDefinitions object, if the used WSDL description had errors, invalid elements were ignored.

If the first tag of the WSDL description used to create WSDefinitions or WSReference objects was not <definitions>, empty web service description objects were created.

If the WSDL description used to create WSDefinitions or WSReference objects did not include the targetNamespace attribute of the <xs:schema> element, the platform set a pseudorandom namespace.

Better diagnostics for WSDL description operations.
Queries.
If a constant stores a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that includes a request to the Value field returns a value of that type.

This change is not implemented in 8.3.7 compatibility mode.

If a constant stored a value of ValueStorage, UUID, or ExternalDataSourceTableRef type, a selection from the constant table that included a request to the Value field returned a value of BinaryData type. Eliminated unexpected system behavior.
Print tools.
The following behavior of the RepresentableDocumentBatch.Print() method is implemented:
  • On Windows:
    • Create a single printer job.
    • Output the entire batch to a file, prompt for the file name before the output.
  • On Linux:
    • If all documents in the batch have identical print settings, use the Windows scenario.
    • If the print settings are different, create a printer job for each document.

This change is not implemented in 8.3.7 compatibility mode.

The RepresentableDocumentBatch.Title, property is implemented. It is used for generating the batch presentation.

The RepresentableDocumentBatch.Print() method created a job for each document in a batch. Improved printing of document batches.
Data composition system.
Text and Format conditional appearance items are applied to fields of chart grouping templates of data composition systems regardless of the previous Format value (even if the previous value is taken from the data composition system). Text conditional appearance item has higher priority than Format conditional appearance.

This change is not implemented in 8.3.7 compatibility mode.

Text and Format conditional appearance items were applied to fields of chart grouping templates of data composition systems only if the Format conditional appearance was not applied to those fields earlier. Eliminated unexpected system behavior.
Data composition system.
The MarkNegatives conditional appearance property is only used if this property is set to True and the Use conditional appearance property is also set to True.

This change is not implemented in 8.3.7 compatibility mode.

The MarkNegatives conditional appearance property was only used if the Use conditional appearance property was set to True. Eliminated unexpected system behavior.
Data composition system.
In the query language, the CASE operation result is based on all expression types from all THEN branches of that expression.

This change is not implemented in 8.3.7 compatibility mode.

In the query language, the calculation of CASE operation result ignored all THEN branches that included constant expressions with NULL values. Eliminated unexpected system behavior.
Full-text search.
The option to set a size limit for data indexed for the full-text search is implemented. The default size limit is 1 MB.

For the FullTextSearchManager object, the SetMaxIndexedDataSize() and GetMaxIndexedDataSize() methods are implemented.

The <FTEXTSKIP> technological log event is implemented.

This change is not implemented in 8.3.7 compatibility mode.

The option to set a size limit for data indexed for the full-text search was not available. All infobase data was indexed. You can limit the full-text search scope by excluding large blocks of data you do not need to search. This increases the performance of full-text search indexing and reduces the index size.
Client application.
Internet-enabled functionality.
Administration tools.
The algorithm that retrieves the list of infobases and platform updates over HTTPS no longer uses the cacert.pem file, which is included in the platform distribution kit.

On Linux, the platform gets certificates from the certification centers specified in the operating system. On Windows, the platrorm uses the operating system root certificate store.

On Windows, the platform used the cacert.pem file and the operating system root certificate store in order to check an HTTPS connection.

On Linux, the platform used the cacert.pem file only.

Simplified administration of platform update over HTTPS.
Linux.
System requirements.
The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system is refactored. The fontconfig library is used to get the list of fonts. This library is included in the system requirements.

The list of directories used for storing fonts is removed from 1C:Enterprise documentation.

The algorithm that generates the list of fonts available to 1C:Enterprise on Linux operating system used a fixed directory list, which was described in 1C:Enterprise documentation.

The fontconfig library was not used for getting the list of fonts.

Extended the list of fonts available to 1C:Enterprise on Linux operating system. Simplified 1C:Enterprise administration.
System requirements.
The type specified for a data composition schema parameter affects the type of query fields that use this parameter.

This change is not implemented in 8.3.7 compatibility mode.

The type specified for a data composition schema parameter did not affect the type of query fields that used this parameter. Data displayed in reports better matches the input parameters.
Dynamic lists.
The dynamic list implementation is refactored in order to increase its quality. The list of virtual dynamic list fields that are not available for use in filter, grouping, and order settings is extended.

If the main dynamic list table does not have key fields (according to 1C:Enterprise script object model) and a grouping is set for this table, an error is generated.

When a filter, sorting, or grouping by a field that is not included in a query is specified using 1C:Enterprise script, an error informing that the field is not found is displayed.

The list of restrictions to queries used to generate dynamic lists is modified.

Dynamic list sorting specifics are described in the documentation.

The description of algorithms that dynamic lists use for getting data is changed.

The standard row picture is generated based on the standard attributes. If a query includes fields whose aliases are identical to standard attribute names and these fields store other data, these fields are not used in standard picture generation.

If a dynamic list filter cannot be converted to a query language expression, an error is generated.

Dynamic list column data that is not displayed and does not have the Use always property set is not sent to the client. Client access to such columns is not available.

If a dynamic list column has the Use always property but the current user does not have the View right for that column, the column data is not sent to the client. Client access to such columns (using the CurrentData property or the RowData() method) is not available.

Automatic dynamic list filters for standard Owner, Parent, Date, Period, and IsFolder fields are applied using data composition system tools.

Automatic dynamic list filters for key fields can be applied using data composition system tools or using direct addition of main table filter conditions to query texts.

When a filter is applied using data composition system tools, it can be applied in nested queries and virtual table parameters. This can significantly change the dynamic list data selection result (compared to the result obtained in 8.3.7 compatibility mode).

The detailed description of all the changes listed above is included in the documentation.

This change is not implemented in 8.3.7 compatibility mode.

The following virtual fields were not available in dynamic list sorting and grouping settings: DataVersion, PredefinedDataName, tabular sections fields, and fields having the following types: Type, String (unlimited length), and BinaryData (unlimited length).

The list of restrictions to the grouping and ordering settings was different and it was not full.

If the main dynamic list table did not have key fields (according to 1C:Enterprise script object model) and a grouping was set for this table, the content of data to be displayed was undefined.

When a filter by a field that was not included in a query text was set, the filter might be applied without displaying any errors, or ignored. If grouping or sorting by a field that was not included in a query was specified using 1C:Enterprise script, the field was ignored. The list of restrictions to queries used to generate dynamic lists was different.

The list of dynamic list sorting specifics was not documented. The description of algorithms that dynamic lists used for getting data was different.

If a dynamic list query had fields with aliases matching the names of standard attributes used to generate standard row pictures, they were used in the generation of standard pictures (except the IsFolder attribute). If a dynamic list filter could not be converted to a query language expression, the filter was applied by data composition schema processor after getting the data, and this might reduce the amount of displayed data.

If dynamic list settings included grouping or sorting fields that were unavailable (before applying rights and functional options), these fields were ignored.

In some scenarios dynamic list column data that was not displayed and did not have the Use always property set was sent to the client.

If dynamic list column had the Use always property but the current user did not have the View right for that column, the column data was sent to the client. In this scenario the default values of specific data types were used as column values.

Automatic dynamic list filters for key fields and for standard Owner, Parent, Date, Period, and IsFolder fields were applied by direct addition of their conditions to query texts.

Improved quality and reliability of dynamic lists. More details about dynamic list specifics are added to the documentation.
Background and scheduled jobs.
When a nonserializable value is passed to BackgroundJobs.Execute() method as a background job parameter, the background job is not started and an exception is raised.

This change is not implemented in 8.3.7 compatibility mode.

When a nonserializable value was passed to the BackgroundJobs.Execute() method as a background job parameter, the background job was started and the Undefined value was stored to that parameter. This did not raise any exceptions. The start of background jobs complies with the global error diagnostic rules.
Administration tools.
During an unexpected shutdown of the thin client, the dump generation includes taking a screenshot (prntscrn attribute of dump element of logcfg.xml file).

During an unexpected shutdown of the thin client, the dump generation did not include taking a screenshot. Eliminated unexpected system behavior.
Queries.
The result of division by NULL is treated as a number of unspecified length . This number cannot be used in operations that do not accept numeric operands (such as AND, OR, NOT).

This change is not implemented in 8.3.7 compatibility mode.

The result of division by NULL was not treated as a number and therefore could be used in operations that did not accept numeric operands (such as AND, OR, NOT). Eliminated unexpected system behavior.
Managed forms.
Interface.
The approach to processing the closing of applications and managed forms is changed:
  • The new "exit application" mode is implemented. It requires special processing in the BeforeClose and OnClose managed form event handlers.
  • Opening windows and executing server calls is not allowed in BeforeExit and OnExit managed application event handlers, and also in BeforeClose and OnClose managed form event handlers (provided that the form is in the "exit application" mode).
  • The option to generate a text message prompting the user to confirm or cancel the exit is implemented (in the web client all messages are combined in a single dialog box).

This approach is described in detail in the documentation.

For BeforeClose managed form event handler, the Exit and WarningText parameters are implemented. For OnClose managed form event handler, the Exit parameter is implemented. If BeforeClose or OnClose managed form event handler has the Exit parameter, in version 8.3.7 compatibility mode the parameter is set to Undefined. For BeforeExit managed application module event handler, the WarningText parameter is implemented.

This change is not implemented in 8.3.7 compatibility mode.

Depending on the modality usage mode, different approaches to closing managed forms and the main application window were used.

In some scenarios (especially in the web client) these approaches led to errors that were hard to detect and fix.

Unified approach to closing forms and the main application window, which provides acceptable user interaction capabilities in all client applications.

The implemented platform behavior conforms to the methodology and technical requirements of modern web browsers.

Administration tools.
Client application installation.
When an infobase that has a platform version specified in a local or global list of infobases is started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version is performed regardless of the presence of /AppAutoCheckVersion command-line option. If a version that is not available on the local computer is specified and this version cannot be installed, an attempt to run the infobase with the latest 1C:Enterprise version is made

During the client application update over HTTP, the check for operating system user right to perform this operation is disabled. If the user does not have sufficient rights for installing the client application, the UAC dialog box prompting to confirm the installation on behalf of a user that has administrative rights is displayed. Error diagnostics during the download and installation of the client application distribution kit over HTTP is improved.

In the /AppAutoCheckVersion command-line option, you can explicitly specify whether the search for a specific 1C:Enteprise version is performed.

When an infobase was started using 1cv8, 1cv8c, or 1cv8s, the search for the specified version was only performed if the command line included the /AppAutoCheckVersion option. During the client application update over HTTP, the check for operating system user right to perform this operation was performed. The usability of selection and update of the client application used to access a specific infobase is improved.

Improved reliability of automatic thin client updates over HTTP.

Administration tools.
When the thin client is installed from a custom distribution kit, a single 1cestart shortcut is created in the 1C:Enterprise folder. When the thin client was installed from a custom distribution kit, the 1C:Enterprise folder included 1cestart shortcut and the Advanced folder with subfolders for each installed 1C:Enterprise version. Reduced number of 1C:Enterprise startup options available after the installation of the thin client.
Administration tools.
In the client application startup command line, the rules for parsing mandatory parameters are modified. If an option that has a mandatory parameter is specified, the parameter must be also specified (or the option must be omitted). Parameters beginning with slash marks "/" are allowed. In the client application startup command line, the rules for parsing mandatory parameters were different. Mandatory option parameters could be omitted. Parameters beginning with slash marks "/" (full file name on Linux) could be treated as command-line options. Eliminated unexpected system behavior.
Administration tools.
1C:Enterprise documentation and Designer help include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode, which were previously missing.

For the infobase creation mode (CREATEINFOBASE), new /DumpResult option is implemented. It enables writing the operation result to a file.

In the file mode, batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option automatically creates an infobase if the database file is not available in the directory.

1C:Enterprise documentation and Designer help did not include the descriptions of /Out, /L, /VL, and /O options for the CREATEINFOBASE startup mode.

In the file mode, during the batch Designer startup with /RestoreIB and /LoadCfg options together with the /DisableStartupDialogs option, if the dababase file was not found in the specified directory, the user was asked for the confirmation of further actions.

Improved 1C:Enterprise documentation and Designer help. Simplified batch Designer startup in some usage scenarios.
Data composition system.
If a data set field of a data composition schema has an ordering expression specified and the data composition settings include ordering by this field (Descending), the direction speficied in the ordering expression is reversed.

This change is not implemented in 8.3.7 compatibility mode.

If a data set field of a data composition schema had an ordering expression specified, ordering for this field was always taken from the ordering expression, while the direction specified in the field settings was ignored. Eliminated unexpected system behavior.
Managed locks.
Accounting registers.
Managed locks that are set for writing accounting register records in the LockForUpdate mode are set by values of nonturnover extra dimensions only.

When you set a lock for further operations with balances, it is recommended that you do not specify turnover extra dimension values (you can use the LockForUpdate property or explicitly use a managed lock). When you set a lock for further operations with turnovers, specify all the required extra dimenstion values, including the values of turnover extra dimensions (use the managed lock explicitly).

This change is not implemented in version 8.3.7 compatibility mode.

Managed locks that were set for writing accounting register records in the LockForUpdate mode included locks by all extra dimension values. The behavior of LockForUpdate property of accounting register object is better suited for solving typical tasks. In the LockForUpdate mode, the resulting lock does not inlcude turnover extra dimensions, which fits the frequently used scenarios where the lock is used to check the balances but not the turnovers.
Queries.
In a query, if a single system enumeration is retrieved and it is not combined with other types, the GROUP BY operation groups the values of this field regardless of the enumeration value source.

A similar behavior is implemented for UUIDs and references to external data source tables.

This change is not implemented in 8.3.7 compatibility mode.

In a query, if a single system enumeration was retrieved and it was not combined with other types, the GROUP BY operation might not group the values of this field (depending on the enumeration value source). Eliminated unexpected system behavior.
DBMS operations.
For Microsoft SQL Server DMBS, types of table fields that store some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) are changed. New field types are used if no compatibility mode is selected and only after restructuring configuration objects.

To perform database table restructuring with modification of field types, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair).

This change is not implemented in 8.3.7 compatibility mode.

For Microsoft SQL Server DMBS, table fields that stored some configuration attribute types (date and time, strings of unlimited length, and binary data of unlimited length) had different types. Better mapping between the stored types and Microsoft SQL Server table field types.
DBMS operations.
For all DBMS, the structure of indexes by fields of composite type is modified. This reduces the total number of indexes. Such indexes are built if no compatibility mode is selected and only after restructuring configuration objects.

To perform database table restructuring with index update, specify the required compatibility mode and restructure the infobase in Designer (on the Administration menu, click Verify and repair).

This change is not implemented in 8.3.7 compatibility mode.

For all DBMS, the structure of indexes by fields of composite type was different. Reduced number of indexes for tables storing objects with fields of composite types. This increases the performance of operations with these object types.
Configuration extensions.
When a background job is executed, all the configuration extensions available in the session that startes the job are also attached in the background job session. This change is not implemented in 8.3.7 compatibility mode.

For ConfigurationExtensionsManager object, the ExecuteBackgroundJobWithDatabaseExtensions method is implemented. It duplicates the background job execution procedure implemented in earlier 1C:Enterprise versions.

When a background job was executed, all the configuration extensions available in the infobase were attached in the background job session. Background job execution environment is closer to the parent session environment.
Managed forms.
In the thick and thin clients, when a user starts typing in a cell of a managed form table, the AutoComplete event is fired.

This change is not implemented in version 8.3.7 compatibility mode.

In the thick and thin clients, when a user starts typing in a cell of a managed form table, the StartChoice event is fired. The behavior of the input field in the scenario where a user starts typing in a table cell is uniform with other input scenarios.
Technological log.
The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file is added to the documentation. Adding more than 20 <LOG> elements can impact the platform performance. The recommendation to have no more than 20 <LOG> elements in the logcfg.xml file was absent from the documentation. The recommendation to avoid inefficient technological log usage scenarios is added to the documentation.
Automated testing.
A sections panel that is not displayed in the main window because it contains no items is no longer included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method. A sections panel that was not displayed in the main window because it contained no items was included in the list of subordinate objects returned by the TestedWindowCommandInterface.GetChildObjects() method. Eliminated unexpected system behavior.
Automated testing.
The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list (instead of accessing it by index) is added to the documentation. The recommendation to use FindObject() and FindObjects() methods to access a required item of a subordinate object list was absent from the documentation. Improved 1C:Enterprise documentation.
Managed forms.
The OnClose event handler and the notification specified in the OnCloseNotifyDescription form property are not called when a managed form is closed using the Close() method called in the OnOpen event handler.

This change is not implemented in 8.3.5 compatibility mode.

When a managed form was closed using the Close() method called in the OnOpen event handler:
  • In the web client, the OnClose event handler and the notification specified in the OnCloseNotifyDescription form property were not called.
  • In the thin client, the OnClose event handler and the notification specified in the OnCloseNotifyDescription form property were called.
Unified client application behavior.
Managed forms.
The documentation describes the following platform behavior: when a value is assigned to a variable that is not declared earlier and has a name identical to a property name available in the current context, this can generate a runtime error or a configuration check error. It is recommended that you declare variables with such names using the Var operator to eliminate possible errors. The documentation did not contain a clear description of this scenario. The documentation contains a clear description of a possible scenario and provides recommendations for eliminating possible issues.
Window-based interface.
The order of elements in the collection returned by the GetWindows() method is changed. The documentation and the Syntax Assistant state that the order of elements in that collection does not follow any specific rule and application algorithms must not rely on that order. The documentation did not state that the order of items in the collection returned by the GetWindows() method does not follow any specific rule. The documentation provides more detail about the GetWindows() method.
XML and XDTO support.
An attempt to write an invalid qualified element name generates an exception.

This change is not implemented in 8.3.6 and 8.3.7 compatibility modes.

An attempt to write an invalid qualified element name did not generate an exception. This might produce an invalid XML file. Eliminated unexpected system behavior introduced in version 8.3.6.
Dynamic lists.
If the current user does not have the View right for a dynamic list key field, an attempt to get dynamic list data generates an access violation error.

Information for technical support includes the list of fields that cannot be accessed due to insufficient rights.

This change is not implemented in 8.3.7 compatibility mode.

If the current user did not have the View right for dynamic list key fields, this did not affect the list availability. If a form had conditional formatting based on these key fields, it could not be opened. Eliminated unexpected system behavior.
Dynamic lists.
In the source of available data composition system settings for dynamic lists, the following fields are not available for filtering, sorting, or grouping:
  • Fields subordinate to fields that represent aggregate functions of the query language
  • Fields subordinate to fields from other (external) data sources
  • Subordinate characteristic fields of tabular section fields

The search initiated by typing a search string excludes reference fields that represent aggregate functions of the query language.

This change is not implemented in 8.3.7 compatibility mode.

In the source of available data composition settings for dynamic lists, the following fields were available for filtering, sorting, or grouping:
  • Fields subordinate to fields that represented aggregate functions of the query language
  • Fields subordinate to fields from other (external) data sources
  • Subordinate characteristic fields of tabular section fields

When a filter by any of these fields was applied, a dynamic list might display incorrect data (some data or all data might be missing).

An attempt to search in reference fields that represented aggregate functions of the query language initiated by typing a search string might generate errors. If errors we not generated, a dynamic list might display incorrect data (some data or all data might be missing).

The search intiated by typing a search string in dynamic lists is improved.

Reduced number of errors that did not have clear descriptions.

Dynamic lists.
In 1C:Enterprise mode, in a dynamic list with a custom query and the main table specified, the availability of main table fields and their subordinate fields for filtering does not depend on the availability of these fields in the dynamic list query. If main table fields are absent from the query text, they are added implicitly.

If a dynamic list query text includes a field with alias identical to an alias of a main table field, this field is used in the filter, regardless of whether the fields themselves are identical.

Fields having multiple paths (in different 1C:Enterprise script languages) are only available in the current 1C:Enterprise script language.

This change is not implemented in 8.3.7 and earlier compatibility modes.

Only fields available in a query text and standard main table fields (such as Ref) were available for filtering. A filter that included unavailable fields with names indentical to main table field names might be applied without any errors generated. For a dynamic list with a custom query and the main table specified, you can include main table fields that are absent from the query text in choice parameters and choice parameter links.
Accumulation registers.
Accounting registers.
Eliminated unexpected system behavior during the calculation of accumulation register and accounting register totals in scenarios where a dimension list includes a dimension of String type and an index by dimensions includes more that 16 database fields.

When you migrate to 1C:Enterprise version 8.3.8 or later, it is recommended that you use the data processor available for download at 1c-dn.com (Read more.). The data processor determines whether additional actions are required.

If they are required, after the migration perform infobase verification and repair with Check logical infobase integrity and Recalculate totals check boxes selected, or use the cluster administration console (1cv8a). The latter option is recommended because it is faster.

Accumulation register and accounting register totals might be calculated incorrectly in scenarios where a dimension list included a dimension of String type and an index by dimensions included more that 16 database fields. Eliminated unexpected system behavior.
Internet-enabled functionality.
Web client, web service, and HTTP service publishing tools.
The option to block redirection to potentially harmful sites after completing an OpenID provider operation is implemented. In the default.vrd file, the <returnto> element (subordinate to <provider> element) is implemented. It contains the list of allowed redirection URLs.

Note that publishing OpenID providers from Designer does not support <returnto> elements (existing elements of this type are deleted and new ones are not generated). You have to add these elements manually.

If you migrate to a new 1C:Enterprise verson, requests to OpenID providers that include the openid.return_to parameter will return HTTP error 400.

To eliminate this issue, in the default.vrd file, add the required number of <returnto> elements with available redirection URLs.

The option to affect redirection after completing OpenID provider operations was not provided. Improved security of OpenID provider operations.

Comments
0
Add comment