<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.infra-repository.org/oiar-2013/index.php?action=history&amp;feed=atom&amp;title=BV.Identity_Validation.SAP</id>
	<title>BV.Identity Validation.SAP - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.infra-repository.org/oiar-2013/index.php?action=history&amp;feed=atom&amp;title=BV.Identity_Validation.SAP"/>
	<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar-2013/index.php?title=BV.Identity_Validation.SAP&amp;action=history"/>
	<updated>2026-05-06T14:27:40Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.40.0</generator>
	<entry>
		<id>https://www.infra-repository.org/oiar-2013/index.php?title=BV.Identity_Validation.SAP&amp;diff=85&amp;oldid=prev</id>
		<title>Jan Schoonderbeek: start</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar-2013/index.php?title=BV.Identity_Validation.SAP&amp;diff=85&amp;oldid=prev"/>
		<updated>2012-11-11T23:22:21Z</updated>

		<summary type="html">&lt;p&gt;start&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Maturity|2}}&lt;br /&gt;
{{Pageheaderbox4BBV&lt;br /&gt;
|name=Identity Validation SAP&lt;br /&gt;
|implementsBBT=BT.MW.Identity Validation&lt;br /&gt;
|environment=MW.ENV.Data Centre.Back-end&lt;br /&gt;
|version=0.21&lt;br /&gt;
|owner=S.A.D. Jumelet&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Description Area&lt;br /&gt;
|description=SAP Authentication (native).&lt;br /&gt;
|annotate=yes&lt;br /&gt;
}}&lt;br /&gt;
{{Purpose section&lt;br /&gt;
|text=The purpose is to authenticate a user that requests access to a SAP application against the proprietary SAP Authentication Application either in a local solution (UA) of a central (shared) solution (CUA). &lt;br /&gt;
&lt;br /&gt;
If Single Sign On is required, CUA (and TAM) are required.&lt;br /&gt;
The user base is also a determiner between UA and CUA. If the user base is internal (ArchiSurance own or hired personnel) either the UA or CUA option can be used. If the user base is external of a mix of internal and external UA is used. Single Sign is then only possible if an exception is granted for the external users.&lt;br /&gt;
}}&lt;br /&gt;
{{Section&lt;br /&gt;
|header=Characteristics &amp;amp;amp; indications of usage&lt;br /&gt;
|text=The authentication data are maintained and deployed from the Central User Administration (CUA). This will provide the organization with a single point of administration and an excellent overview which user is authorized on which systems and for which activities. The Authentication and Authorization facilities are integrated in one application.&lt;br /&gt;
}}&lt;br /&gt;
Note: in the text below, we still need to add elements&lt;br /&gt;
* Oracle&lt;br /&gt;
* High Availability software&lt;br /&gt;
{{BBV Elements prescription}}&lt;br /&gt;
{{Elements Prescription Table}}&lt;br /&gt;
{{Element Prescription Row&lt;br /&gt;
|element=EL.Central User Administration (CUA)&lt;br /&gt;
|prescription=must&lt;br /&gt;
|reason=Software component&lt;br /&gt;
}}&lt;br /&gt;
{{Element Prescription Row&lt;br /&gt;
|element=EL.User Administration (UA)&lt;br /&gt;
|prescription=must&lt;br /&gt;
|reason=Software component&lt;br /&gt;
}}&lt;br /&gt;
{{Element Prescription Row&lt;br /&gt;
|element=EL.Red Hat Enterprise Linux SmartHat&lt;br /&gt;
|prescription=must&lt;br /&gt;
|reason=Cost and the SAP Product Availability Matrix&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{BBV Quality Description&lt;br /&gt;
|adaptability=HSC&lt;br /&gt;
|scalability=up&lt;br /&gt;
|manageability=Medium&lt;br /&gt;
|accountability=SP&lt;br /&gt;
|availability=High&lt;br /&gt;
|integrity=Low&lt;br /&gt;
}}&lt;br /&gt;
{{BBV Text Footer}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
</feed>