• Home
• org.ow2.authzforce
• authzforce-ce-pap-dao-flat-file
• 15.0.0
• source code

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

force.authzforce-ce-pap-dao-flat-file.15.0.0.source-code.org.ow2.authzforce.pap.dao.flatfile.properties.xsd Maven / Gradle / Ivy

	
		
			Data Model for policy domain properties used by the AuthZForce PAP DAO based on flat file database.
			

				XML schema versioning: the 'version' attribute of the root 'schema' element identifies the Major.Minor.Patch version of this schema. The Major.Minor part must match the Major.Minor part of the
				first compatible version of authzforce-ce-pap-dao-file library. The Patch version is used for any backwards-compatible change. The Minor version is incremented after any change that is NOT
				backwards-compatible. (As a result, the authzforce-ce-pap-dao-file library's minor version is incremented as well.)
				The Major.Minor version part must be part of the target namespace - but not the
				Patch
				version - to separate namespaces that are not backwards-compatible.
			
		
	
	
		
			
		
		
			
				
					Same function as in SCIM schema:
					An identifier for the Resource as defined by the Service Consumer. The externalId may simplify identification of the
					Resource between Service Consumer and Service
					provider by allowing the Consumer
					to refer to the Resource with its own identifier, obviating the need to store a local mapping between the local
					identifier of the Resource and the identifier
					used by the Service Provider. Each
					Resource MAY include a non-empty externalId value. The value of the externalId attribute is always issued be the
					Service Consumer and can never be specified by
					the Service Provider. The Service
					Provider MUST always interpret the externalId as scoped to the Service Consumer's tenant.
				
			
		
		
				
					Maximum number of policies. No limit if this
						attribute is missing.
					
				
			
			
				
					Maximum number of versions per policy. No limit
						if this attribute is missing.
					
				
			
			
				
					True iff versions are automatically removed to
						keep the number of versions under 'maxVersionCountPerPolicy',
						especially when this max is already reached. The strategy for
						removing versions is implementation-specific; e.g. implementations
						may remove the oldest versions first.
						Implementations must make
						sure it does not
						break the 'rootPolicyRef' defined previously or
						any Policy
						reference from it (direct or indirect).