Skip to end of banner
Go to start of banner

SecurityPolicy

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

This document describes the usage of SecurityPolicy in the Nordic NeTEx profile.

Usage of the SecurityPolicy parameter is currently only supported on the elements SalesOfferPackage, SalesOfferPackageElement and FareProduct in Entur. If used on any other element the SecurityPolicy parameter will be ignored.

The SecurityPolicy parameter should be used by the fare product owner to define the acceptable risk level for customer accounts that can hold FareContracts for FareProducts and SalesOfferPackages.

Order of precedence

If SecurityPolicy parameters are provided on SalesOfferPackage as well as SalesOfferPackageElement and/or FareProduct as shown in the diagram above, only one of the SecurityPolicy parameters will be considered for the SalesOfferPackage and all of its parts when issuing the FareContract. In order of precedence, the SecurityPolicy will be selected from

  1. SalesOfferPackage

  2. SalesOfferPackageElement

  3. FareProduct

Most restrictive parameter

If SecurityPolicy parameters are provided on more than one element of the same type as shown in the diagram above, the most restrictive SecurityPolicy parameter will be selected for the entire SalesOfferPackage and all of its parts.

Parameter combinations

If SecurityPolicy parameters are used in combination with other validity or limiting parameters it must be possible to determine which SecurityPolicy parameter should be used when offering a SalesOfferPackage for a specific customer journey. To enforce the fulfilment of this requirement in the context of an offer generating system, use the GenericParameterAssignment requiredType and requiredInContext to require the SecurityPolicy element type.

  • No labels