https://wikitest.augmensys.com/api.php?action=feedcontributions&feedformat=atom&user=DSTUBIK Wiki Test / Augmensys - User contributions [en]2026-04-30T20:10:48ZUser contributionsMediaWiki 1.24.2https://wikitest.augmensys.com/index.php?title=SYSCLS_SHOWPROPERTIES&diff=23666SYSCLS SHOWPROPERTIES2022-05-10T13:47:48Z<p>DST: </p>
<hr />
<div>{{ClassificationInfoBox<br />
| title = ShowProperties<br />
| name = {{PAGENAMEE}}<br />
| inheritance = -<br />
| namespace = System.Classification.Content<br />
| purpose = Classify an object Show Properties<br />
| version = 2.4.4+<br />
| id = {F47ABD78-2EFF-493E-8D00-9A99D4F745A7}<br />
}}<br />
<br />
Objects having this classification will show their properties (as selected tab) when being displayed on the client.<br />
<br />
<br />
<br />
== See also ==<br />
* [[SYSCLS_SHOWDOCUMENTS]]<br />
<br />
[[Category:Classifications|SYSCLS SHOWPROPERTIES]]</div>DSThttps://wikitest.augmensys.com/index.php?title=SYSCLS_SHOWDOCUMENTS&diff=23665SYSCLS SHOWDOCUMENTS2022-05-10T13:47:26Z<p>DST: </p>
<hr />
<div>{{ClassificationInfoBox<br />
| title = ShowDocuments<br />
| name = {{PAGENAMEE}}<br />
| inheritance = -<br />
| namespace = System.Classification.Content<br />
| purpose = Classify an object Show Documents<br />
| version = 2.4.4+<br />
| id = {3201EA50-88A8-4CB7-B3D7-2C9A1646167A}<br />
}}<br />
<br />
Objects having this classification will show their child documents (as selected tab) when being displayed on the client.<br />
<br />
<br />
<br />
== See also ==<br />
* [[SYSCLS_SHOWPROPERTIES]]<br />
<br />
[[Category:Classifications|SYSCLS SHOWDOCUMENTS]]</div>DSThttps://wikitest.augmensys.com/index.php?title=Annotation_and_HotSpot&diff=23626Annotation and HotSpot2022-04-26T07:20:59Z<p>DST: /* Annotations */</p>
<hr />
<div>HotSpotting summarizes a general technique in {{UBIK}}, that allows to overlay data on the visual representation of other {{UBIK}} objects. The overlaid data can be of quite a variety, starting from Annotations (also known as Redlining or Inking) over Links/Cross-references between objects, to {{UBIK}} Properties in all their different possible types and appearances. <br />
While HotSpotting is an abstract approach that could be applied to any kind of {{UBIK}} object, the client currently only supports displaying and interacting with HotSpots on Document objects.<br />
<br />
==Overview==<br />
HotSpotting consists of 3 main elements, the Target, the Layer(s) and the HotSpots:<br />
<br />
===Target===<br />
A HotSpotting target can be basically any {{UBIK}} object that holds the classification [[SYSCLS HOTSPOT|HotSpotting target]]. In most of the use cases, this target will be [[FILEDOCUMENT|file document]] or a derivative of that class.<br />
<br />
===Layer===<br />
A layer can be envisioned as a transparent film that is overlaid on the target and contains the actual HotSpots. Technically their can be as many layers as desired, overlaying each others.<br />
A layer covers the whole physical area of its target, i.e. the dimensions of the page of a document.<br />
<br />
===HotSpot/Annotation===<br />
A HotSpot is a single data object that sits on a layer and typically has a visual representation, such as the value of a property it represents. <br />
<br />
==HotSpots==<br />
All HotSpots have in common that they know<br />
* on which layer they sit<br />
* their offset relative to the Top/Left corner of the layer<br />
* their width and their height<br />
* their shape (angular or round/elliptical)<br />
<br />
When it comes to their representations and capabilities, there are different types that support certain use-cases and/or types of backing {{UBIK}} objects or properties:<br />
<br />
===InputSpot===<br />
An InputSpot is a link to a property from a {{UBIK}} Object. It displays the value of the property and reacts to user interaction, e.g. with popping up the property editor when tapped on it. Any existing {{UBIK}} property can be represented as an InputSpot.<br />
<br />
===MediaSpot===<br />
A MediaSpot is a specialization of an InputSpot that works with properties that can hold media (Audio/Video) data. <br />
<br />
===SignatureSpot===<br />
A SignatureSpot is a specialization of an InputSpot that works with properties of type [[MetaProperty#Signature|Signature]]. It allows for graphically signing of objects.<br />
<br />
===ScanSpot===<br />
A scan spot is a HotSpot that scans the area it covers using OCR. So when the user moves it around a document or resizes it, it will write the recognized OCR text to its value.<br />
<br />
==Annotations==<br />
An Annotation is a collection of Ink strokes that sits on a layer and typically represents redlining or additional information to a document, like a diagram or a photo.<br />
<br />
<br />
----<br />
<br />
<br />
==How to enable Hotspotting in the UI==<br />
In order to enable the hotspotting feature in the newest Ubik4.0 release you have to do the following.<br />
Go to the UBIKDocumentArea.xaml and add the 'HotspotButtonVisibility="Visible"' line to the UBIKPdfViewer.<br />
The <ctrls:UBIKPdfViewer> should look like the following:<br />
<br />
<source lang = "xml"><br />
<ctrls:UBIKPdfViewer<br />
HotspotButtonVisibility="Visible"<br />
AutoSave="{Binding DataContext.ApplicationSettings.CurrentProfile.ContentSettings.AutoSaveMode, ElementName=pdfBorder}"<br />
ContentViewModel="{Binding Path=DataContext, ElementName=pdfBorder}"<br />
HotSpotTappedCommand="{Binding DataContext.HotSpotViewModel.HotSpotTappedCommand, ElementName=pdfBorder}"<br />
HotSpotTemplateSelector="{StaticResource DefaultHotSpotTemplateSelector}"<br />
PageChangedCommand="{Binding DataContext.HotSpotViewModel.PageChangedCommand, ElementName=pdfBorder}" /><br />
</source><br />
<br />
<br />
==See also==<br />
* [[SYSCLS ANNOTATION]]<br />
* [[SYSCLS HOTSPOT]]<br />
* [[HotSpotting (Plugin)]]</div>DSThttps://wikitest.augmensys.com/index.php?title=XAML_Tips&diff=23594XAML Tips2022-04-08T15:12:49Z<p>DST: /* InvokeOnItemsCommand {{Version/WinXSince|3.6}} */</p>
<hr />
<div>== Functionality related ==<br />
<br />
=== Attachable behaviors ===<br />
It's quite often that you need to attach behaviors to certain XAML elements. For example, on a Grid, you want to attach a behavior which executes a command upon a Tapped event, or you want to execute a command when a certain property on a UBIK object changes.<br />
<br />
Notice that in the following examples, "Interactivity" and "Core" are both namespaces and you have to make sure that they are defined at the root of your XAMLs:<br />
<br />
<source lang = "xml"><br />
<DataTemplate<br />
...<br />
xmlns:Core="using:Microsoft.Xaml.Interactions.Core"<br />
xmlns:Interactivity="using:Microsoft.Xaml.Interactivity"><br />
...<br />
</DataTemplate><br />
</source><br />
<br />
==== Event Triggered ====<br />
With an EventTriggerBehavior, you can react on changes/events of UI Elements:<br />
<br />
<source lang = "xml"><br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<Core:EventTriggerBehavior EventName="Tapped"><br />
<Core:InvokeCommandAction Command="{Binding NavigateToChildrenCommand}" /><br />
</Core:EventTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br />
==== Data Triggered ====<br />
If you want to react on changes of the underlying data (ViewModel), you can use DataTriggerBehavior instead. The following example, when used in the ''UBIKSplashArea'' template, automatically navigates to the root objects once the login process is finished and the user was successfully authenticated:<br />
<br />
<source lang = "xml"><br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<Core:DataTriggerBehavior Binding="{Binding IsLoggedIn}" Value="True"><br />
<Core:InvokeCommandAction Command="{Binding NavigateToRootPageCommand}" /><br />
</Core:DataTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br />
<br />
=== Fit mode ===<br />
If you are using the standard app without XAML customizings, the [[UBIK_WinX_Client_Basics#Fit_Mode|fit mode]] feature should work out of the box.<br />
However, when using a FlipView for displaying documents in your customized XAMLs, you must make sure to include the following binding to the FlipView's ItemTemplate so that the fit modes are properly applied.<br />
<br />
<source lang = "xml"><br />
<DataTemplate<br />
... <br />
xmlns:hs="using:UBIK.WinX.HotSpotting.Document"><br />
...<br />
<Grid.Resources><br />
...<br />
<DataTemplate x:Key="FlipDocItemTemplate"><br />
...<br />
<hs:Document<br />
...<br />
FitMode="{Binding DocumentViewModel.FitMode}" /><br />
</DataTemplate><br />
</Grid.Resources><br />
</DataTemplate><br />
</source><br />
<br />
=== Content creation === <br />
{{Version/WinXSince|3.5.5}}<br />
To directly create an object on a child of the current object, you can define a Button as follows. The method "Item.IsTypeCreationAllowed" used in the expression gets the uid of the type that should be created below a child, if a child does not allow the creation of that type underneath it, the child will be hidden in the selection dialog. To actually create the object, the "CreateChildItemCommand" needs to be passed a KeyValueList with two parameters: The Parent-key is the UID or the ContentViewModel of the child underneath the object should be created, the Type-key is the type of object which should be created--this should match the uid passed to the "Item.IsTypeCreationAllowed" method.<br />
<br />
<source lang = "xml"><br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
xmlns:cv="using:UBIK.WinX.UI.CollectionView"<br />
</source><br />
<br />
<source lang = "xml"><br />
<x:String x:Key="PlantMap">Item.IsTypeCreationAllowed(&quot;21fc990a-d064-4bee-8d48-3293351f827a&quot;)</x:String><br />
<cv:ListCollectionView x:Key="PlantMapView" Expression="{StaticResource PlantMap}" ItemsSource="{Binding Children.Items}" /><br />
<br />
<AppBarButton><br />
<AppBarButton.Flyout><br />
<Flyout Placement="Full"><br />
<ListView ItemsSource="{Binding Source={StaticResource PlantMapView}}"><br />
<ListView.ItemTemplate><br />
<DataTemplate><br />
<Button Content="{Binding Header}" Command="{Binding CreateChildItemCommand}" x:Name="CreateButton" Tag="{Binding}"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Parent" Value="6D733909-1742-4110-8619-237849BFE453"/><br />
<uc:KeyValueParameter Key="Type" Value="21fc990a-d064-4bee-8d48-3293351f827a"/><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</DataTemplate><br />
</ListView.ItemTemplate><br />
</ListView><br />
</Flyout><br />
</AppBarButton.Flyout><br />
</AppBarButton><br />
</source><br />
<br />
<source lang = "xml"><br />
<x:String x:Key="PlantMap">Item.IsTypeCreationAllowed(&quot;21fc990a-d064-4bee-8d48-3293351f827a&quot;)</x:String><br />
<cv:ListCollectionView x:Key="PlantMapView" Expression="{StaticResource PlantMap}" ItemsSource="{Binding Children.Items}" /><br />
<br />
<AppBarButton><br />
<AppBarButton.Flyout><br />
<Flyout Placement="Full"><br />
<ListView ItemsSource="{Binding Source={StaticResource PlantMapView}}"><br />
<ListView.ItemTemplate><br />
<DataTemplate><br />
<Button Content="{Binding Header}" Command="{Binding CreateChildItemCommand}" x:Name="CreateButton" Tag="{Binding}"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Parent" Value="{Binding Tag, ElementName=CreateButton}"/><br />
<uc:KeyValueParameter Key="Type" Value="21fc990a-d064-4bee-8d48-3293351f827a"/><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</DataTemplate><br />
</ListView.ItemTemplate><br />
</ListView><br />
</Flyout><br />
</AppBarButton.Flyout><br />
</AppBarButton><br />
</source><br />
<br />
<br/><br />
Additionally, the following optional parameters can be added as well.<br />
* CreateOnly (optional, defaults to false): When set to true, the client will not automatically navigate to the created content, rather automatically save and commit it. If set to true, this overrides the following parameters;<br />
* AutoNavigate (optional, defaults to true): When set to false, the client will not automatically navigate to the created content;<br />
* AutoCommit (optional, defaults to false): When set to true, the change(s) will be saved to the local cache and the database, and then committed to the server.<br />
<br />
=== Creating multiple documents ===<br />
To upload multiple documents at once, the CreateChildItemsCommand can be used. The list of supported command parameters are similar to those of the CreateChildItemCommand (single item). Except that anything other than AutoNavigate=false and AutoCommit=true do not make sense in multi-creation scenario. Therefore, those parameters are fixed and any received from XAML will be ignored.<br />
<br />
<!-- <tabs><br />
<br />
<tab name="UWP">--><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:uc="using:UBIK.WinX.Controls"<br />
Command="{Binding CreateChildItemsCommand}"<br />
Content="Create multiple documents"><br />
<Button.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Type" Value="6170a068-2314-4444-ad62-0da99769a048" /><br />
</uc:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
<!--</tab><br />
<br />
<tab name="Xamarin"><br />
<source lang = "xml"><br />
<Button ...<br />
xmlns:classes="clr-namespace:UBIK.CPL.Classes;assembly=UBIK.CPL"<br />
Command="{Binding CreateChildItemsCommand}"<br />
Content="Create multiple documents"><br />
<Button.CommandParameter><br />
<classes:KeyValueList><br />
<classes:KeyValueParameter Key="Type" Value="6170a068-2314-4444-ad62-0da99769a048" /><br />
</classes:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
</tab><br />
<br />
</tabs>--><br />
<br />
<br />
<br />
<br />
<br />
=== Disable FilloutCriteria ===<br />
{{Version/WinXSince|3.5}}<br />
To enable/disable the automatic filtering of a query based on the ParentObject, there is the possibility to specify EnableFillOutCriteria--if it is not set, it defaults to false. Additionaly "SkipDialog" can be set to true, to not display a dialog.<br />
<br />
<source lang="xml"><br />
<Grid x:Name="selectionGrid" Tag="{Binding MetaUID}"><br />
<Interactivity:Interaction.Behaviors><br />
<Core:EventTriggerBehavior EventName="Tapped"><br />
<Core:InvokeCommandAction Command="{Binding ElementName=ChildAreaGrid, Path=DataContext.AddTemplatableDataCommand}" ><br />
<Core:InvokeCommandAction.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Uid" Value="{Binding Tag,ElementName=selectionGrid}"/><br />
<uc:KeyValueParameter Key="EnableFillOutCriteria" Value="false"/><br />
<uc:KeyValueParameter Key="SkipDialog" Value="false"/><br />
</uc:KeyValueList><br />
</Core:InvokeCommandAction.CommandParameter><br />
</Core:InvokeCommandAction><br />
</Core:EventTriggerBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</source><br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:XAML|XAML Tips]]<br />
[[Category:Xamarin|XAML Tips]]<br />
<br />
=== Hotspotting ===<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
The hotspotting command is used for hotspotting as well as for annotating, to configure the button for hotspotting, the commandparameter "Mode" should be set to "HotSpotting", for annotating the "Mode" should be "Annotate". The parameter commit is optional, if set to true, the changes get automatically persisted when leaving the editing mode.<br />
<br />
<source lang = "xml"><br />
<AppBarToggleButton<br />
IsChecked="{Binding EditingAnnotation, Mode=TwoWay}"<br />
IsEnabled="{Binding IsAnnotatable}"<br />
Command="{Binding HotSpottingCommand}"><br />
<AppBarToggleButton.CommandParameter><br />
<uc:KeyValueList><br />
<uc:KeyValueParameter Key="Mode" Value="Annotate"/><br />
<uc:KeyValueParameter Key="Commit" Value="true"/><br />
</uc:KeyValueList><br />
</AppBarToggleButton.CommandParameter><br />
</AppBarToggleButton><br />
</source><br />
<br />
<br />
<br />
<br />
=== Remember scroll positions of list views ===<br />
<br />
==== Version 3.7 & later {{Version/WinXSince|3.7}} ====<br />
Starting from this version,<br />
* The precision of scroll position remembering is improved(by pixel offsets instead of by items);<br />
* It also works for other scrollable lists (instead of just for content object lists).<br />
<br /><br />
To enable this feature, you should make sure the following.<br />
* The SelectionBoundListView is used instead of the standard ListView. Its {{UBIK}} namespace is <code>UBIK.WinX.Controls</code>;<br />
* The SelectionBoundListView's <code>RememberScrollPosition</code> property is not set to "false"; (It's "true" by default.)<br />
* The SelectionBoundListView's <code>x:Name</code> property value is unique.<br />
<br />
<br />
<br />
<br />
==== Version 3.6 {{Version/WinXSince|3.6}} ====<br />
The UBIK-Client does include a function to remember the position in a list (ListView) when navigating away from it. This function is only available when the list (ListView) has a unique name as a property (x:Name). When browsing back to the previously visited list UBIK scrolls back to the last position. The function does not save scroll positions over different sessions.<br />
Implementing the function to remember the scroll position in a ListView one has to consider that the list elements (Children) could depend on a other UI-element. If the list elements do depend on a other UI-elemente, this element has to be created above the ListView in the XAML.<br />
<br />
<source lang = "xml"><br />
<DataTemplate xmlns:behaviors="using:UBIK.WinX.Behaviors" xmlns:uc="using:UBIK.WinX.Controls"><br />
...<br />
<uc:SelectionBoundListView x:Name="ChildListView"><br />
<Interactivity:Interaction.Behaviors><br />
<behaviors:FirstVisibleItemPersistenceBehavior FirstVisibleItems="{Binding ScrollItems}" /><br />
</Interactivity:Interaction.Behaviors><br />
</uc:SelectionBoundListView><br />
</DataTemplate><br />
</source><br />
<br />
<br />
<br />
<br />
=== MultiBinding {{Version/WinXSince|3.6}} ===<br />
Very often we want to display some UI elements (e.g. a Grid) depending on whether multiple criteria are met. It's much easier to achieve this by using a MultiBindingBehavior like the following.<br />
<source lang = "xml"><br />
<DataTemplate<br />
xmlns:Interactivity="using:Microsoft.Xaml.Interactivity"<br />
xmlns:behaviors="using:UBIK.WinX.Behaviors"><br />
...<br />
<Grid><br />
<Interactivity:Interaction.Behaviors><br />
<behaviors:MultiBindingBehavior Converter="{StaticResource VisLogicAndConverter}" PropertyName="Visibility"><br />
<behaviors:MultiBindingItem Value="{Binding MassEditViewModel, Converter={StaticResource NullToVisConverter}}" /><br />
<behaviors:MultiBindingItem Value="{Binding Documents.Items.Count, Converter={StaticResource ItemCountToVisConverter}}" /><br />
</behaviors:MultiBindingBehavior><br />
</Interactivity:Interaction.Behaviors><br />
</Grid><br />
</DataTemplate><br />
</source><br />
The behavior makes sure the container Grid is set to Visibile only if the mass editing mode is not turned on (MassEditViewModel is null) and the context object has child document(s) (Documents.Items.Count is greater than 0. You can combine any number of binding results (MultiBindingItem) using the VisLogicAndConverter (the name should be self explanatory).<br />
<br />
=== InvokeOnItemsCommand {{Version/WinXSince|3.6}} ===<br />
Available on all ListViewModels, this command allows executing a specified command on a collection of list items. It can be used in combination with features such as [[Mass_Edit_(UBIK_WinX)|mass editing]] and [[XAML_Changes_in_UBIK_WinX_3.5#After_3.5|expression based collection filtering]]. Examples for both combinations are provided below.<br />
<br />
{{Attention|The command specified through the "Command" parameter is executed on list items and, therefore, must be available in the list item contexts (view models). If in doubt, the [[Developer_Mode|developer mode]] can be used to inspect if a command is available in a certain context.}}<br />
<br />
{{Hint|Parameter "Command" and "SelectedItemsOnly" are specific to the InvokeOnItemsCommand. What other parameters to define or whether to define them at all depends on the type of command to be executed on the items.}}<br />
<br />
==== Invoke on selected items ====<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
This example demonstrates how you can use the mass editing feature to select certain objects from the child list and then execute the SetPropertyValueCommand for those selected.<br />
* The example code assumes that the child objects have an editable property called "VALUE" and tries to set 50 as their value;<br />
* You should insert the following code snippet into the default UBIKChildArea template;<br />
* If the parameter "SelectedItemsOnly" is missed or set to "False", the command will be executed on all child items;<br />
* To enable selection, click on the "Mass Edit" button below the property list.<br />
<br /><br />
<source lang = "xml"><br />
<Button<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding Children.InvokeOnItemsCommand}"<br />
Content="Set to 50%"><br />
<Button.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="SelectedItemsOnly" Value="False" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue"><br />
<example:KeyValueParameter.Value><br />
<x:Double>50</x:Double><br />
</example:KeyValueParameter.Value><br />
</example:KeyValueParameter><br />
</example:KeyValueList><br />
</Button.CommandParameter><br />
</Button><br />
</source><br />
<br />
==== Invoke on filtered results ====<br />
<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
<br />
First, you need to setup a filtered list (ListCollectionView) in the Resources section of a UI element (e.g. Grid).<br />
* This list is only available/visible within that UI element (the Grid in this case);<br />
* The ItemsSource uses Children.Items. Use the [[Developer_Mode|developer mode]] if necessary to find out if this is available where you intend to define the list;<br />
* The example expression filters for any items that don't contain the text "EXAMPLE" in their Title texts. You can filter differently by altering the expression.<br />
<br /><br />
<source lang = "xml"><br />
<Grid xmlns:CV="using:UBIK.WinX.UI.CollectionView"><br />
<Grid.Resources><br />
<CV:ListCollectionView<br />
x:Key="Filtered"<br />
Expression="!Item.Title.Contains(&quot;EXAMPLE&quot;)"<br />
ItemsSource="{Binding Children.Items}" /><br />
</Grid.Resources><br />
...<br />
</Grid><br />
</source><br />
<br /><br />
With the filtered list configured, you can then insert the following code snippet to execute the SetPropertyValueCommand for the filtered result items.<br />
* The example code assumes that the child objects have an editable property called "VALUE" and tries to set 50 as their value;<br />
* The "Filtered" refers to the ListCollectionView configured above.<br />
<br /><br />
<source lang = "xml"><br />
<AppBarButton<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding Source={StaticResource Filtered}, Path=ListViewModel.InvokeOnItemsCommand}"<br />
Icon="AllApps"<br />
Label="Set to 50"<br />
Style="{ThemeResource UBIKActionAppBarButton}"><br />
<AppBarButton.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="Command" Value="SetPropertyValueCommand" /><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue" Value="50" /><br />
</example:KeyValueList><br />
</AppBarButton.CommandParameter><br />
</AppBarButton><br />
</source><br />
<br />
<br />
<br />
<br />
==== Support for old styled commands ====<br />
Some old commands might not support KeyValueLists as parameters. In that case, just define the parameter value under the "CommandParameter" key, e.g.<br />
<br /><br />
<source lang = "xml"><example:KeyValueParameter Key="CommandParameter" Value="some string value for example" /></source>.<br />
This single value is then passed as the command parameter instead of the entire KeyValueList.<br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:XAML|XAML Tips]]<br />
[[Category:Xamarin|XAML Tips]]<br />
<br />
=== SetPropertyValueCommand {{Version/WinXSince|3.6}} ===<br />
{{Attention|To use a binding in the KeyValueParameter, it has to be applied like in the example provided here: [[KeyValueList]]}}<br />
<br />
This command existed before but was implemented differently. In the newer version(s), it is improved to provide customizers more control over the things that happen during/after the property value changes.<br />
The available commnad parameters are:<br />
* PropertyName: the name of the property to set a new value to;<br />
* PropertyValue: the value to be set to the above mentioned property;<br />
* OnlyForUnvalidated (optional, defaults to false): When set to true, the value will only be set if the property is not yet validated;<br />
* AutoSave (optional, defaults to false): When set to true, the change(s) will be saved to the local cache and database;<br />
* AutoCommit (optional, defaults to false): When set to true, the change(s) will be committed to the server.<br />
<br />
{{Hint|There's no way to commit changes without saving them locally first. Therefore, the "AutoSave" parameter will be ignored when "AutoCommit" is set to true.}}<br />
<br />
Here's an example of the command usage. It tries to set the property called "VALUE" to a double value 50 regardless of its current state and then automatically save and commit the change.<br />
<br /><br />
<source lang = "xml"><br />
<AppBarButton<br />
xmlns:example="using:UBIK.WinX.Controls"<br />
Command="{Binding SetPropertyValueCommand}"<br />
Icon="Edit"<br />
Label="Set to 50%"<br />
Style="{ThemeResource UBIKActionAppBarButton}"><br />
<AppBarButton.CommandParameter><br />
<example:KeyValueList><br />
<example:KeyValueParameter Key="PropertyName" Value="VALUE" /><br />
<example:KeyValueParameter Key="PropertyValue"><br />
<example:KeyValueParameter.Value><br />
<x:Double>50</x:Double><br />
</example:KeyValueParameter.Value><br />
</example:KeyValueParameter><br />
<example:KeyValueParameter Key="OnlyForUnvalidated" Value="false" /><br />
<example:KeyValueParameter Key="AutoSave" Value="true" /><br />
<example:KeyValueParameter Key="AutoCommit" Value="true" /><br />
</example:KeyValueList><br />
</AppBarButton.CommandParameter><br />
</AppBarButton><br />
</source><br />
<br />
{{Hint|It is advised to provide typed values like <nowiki><x:Double>50</x:Double></nowiki>. But for simple types, you can try writing them in the text format like <nowiki><example:KeyValueParameter Key="PropertyValue" Value="50" /></nowiki> and {{UBIK}} will try to find the right type.}}<br />
<br />
<br />
=== DisplayViewCommand ===<br />
This command can be used to [[Custom_View_(Client)|display cutom views]].<br />
<br />
<br />
== Performance related ==<br />
<br />
=== FlipView ===<br />
When using the FlipView control in your XAML code, it's better to enable [https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/optimize-gridview-and-listview#ui-virtualization UI virtualization]. The difference in performance gets more obvious as the number of items in the FlipView increases. Here's how to enable it.<br />
<br />
<source lang = "xml"><br />
<FlipView<br />
...<br />
VirtualizingStackPanel.VirtualizationMode="Standard"><br />
<Flipview.ItemsPanel><br />
<ItemsPanelTemplate><br />
<VirtualizingStackPanel Orientation="Horizontal" /><br />
</ItemsPanelTemplate><br />
</Flipview.ItemsPanel><br />
</FlipView><br />
</source><br />
<br />
<br />
VirtualizingStackPanel.VirtualizationMode offers two possibilities: Standard & Recycling. In case you are interested, here are their [https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.virtualizationmode?view=netframework-4.7.2 differences].<br />
<br />
[[Category:Client]]<br />
[[Category:WinX]]<br />
[[Category:Xamarin]]<br />
[[Category:XAML]]<br />
<br />
[[Category:Client|XAML Tips]]<br />
[[Category:WinX|XAML Tips]]<br />
[[Category:Xamarin|XAML Tips]]</div>DSThttps://wikitest.augmensys.com/index.php?title=HowTo:Integrate_UBIK_in_an_SSO_Environment&diff=23297HowTo:Integrate UBIK in an SSO Environment2021-09-21T09:46:43Z<p>DST: /* Client */</p>
<hr />
<div>Single Sign On (SSO) allows an end-user to interact with multiple services without logging in more than once. <br />
<br />
This page shows how to integrate {{UBIK}} into such an SSO environment.<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS --><br />
<br />
= Instructions =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
The customer's Identity Provider must know {{UBIK}} as a Service Provider. We need to provide an SSO mediator server in order to relay SSO responses for the client; this is our ACS (Assertion Consumer Service).<br />
<br />
There are two major use-cases for SSO:<br />
* Authentication: Establishing or re-using an SSO session (logging in)<br />
* Authorization: Interaction with external systems (interfacing)<br />
<br />
In order to configure {{UBIK}} for SSO integration, we need to address both.<br />
<br />
== Authentication ==<br />
* In the {{UBIK}} client profile, adjust the SSO relevant settings (enabling SSO and specifying the Identity Provider Endpoint URL for an IdP-initiated flow).<br />
* On the server side, make sure that an SSO Processor is configured able to process the responses from the Identity Provider.<br />
<br />
== Authorization ==<br />
When a {{UBIK}} object is synchronized between client and server, the {{UBIK}} customizing can interact with external systems. There, we might require authorization, and we need to make sure the client provides a respective token. In order to do so, we have to identify the specific authorization use-cases:<br />
* For which types of objects (meta classes) do I need to interact with external systems, requiring SSO authorization?<br />
* For which synchronization operations (e.g., update, commit, create, etc.) do I need authorization?<br />
* Which IdP endpoint is used in this case?<br />
For each resulting combination we have to create an [[SYSCLS_EXTERNALAUTHCONFIG|External Auth Config]] object and give it to the client in the infrastructure list.<br />
<br />
Further, we have to make sure the authorization tokens can be transported to the server. Therefore, add the [[SYSCLS_EXTERNALENTITY|External Entity Classification]] to all meta classes of objects that need external authorization.<br />
<br />
= Studio =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
* Add [[SYSCLS_EXTERNALAUTHCONFIG|External Auth Config]] objects to the client's infrastructure <br />
* Add the [[SYSCLS_EXTERNALENTITY|External Entity Classification]] to all affected meta classes<br />
<br />
= Client =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
* '''Set up an SSO mediator backend server to relay SSO responses to the client'''<br />
<br />
----<br />
<br />
To set up an Authentication Server first go to http://release.augmensys.com/ and download the provided Zip File.<br />
After you downloaded the Zip create a new IIS applicatio (https://docs.microsoft.com/en-us/iis/configuration/system.applicationhost/sites/site/application/).<br />
Open the just created app in your file explorer, unpack the downloaded ZIP file and copy all files of that ZIP into the app-folder.<br />
If IIS prohibites you to copy files you need to first stop the server. After successfully copying the Files you need to Restart/Start the IIS server again.<br />
Now you have set up the Authentication-Backend and it is ready to use.<br />
<br />
<br />
* '''Configure the SSO profile settings respectively'''<br />
<br />
----<br />
The Single-Sign-On implementation introduces three new Profile Settings needed to setup SSO in your environment, namely:<br />
* <EnableSSO>true/false</EnableSSO> This setting, if set to "true" enables the SSO workflow and disable the possibility to authenticate against the UBIK backend.<br />
* <BackendURL>https://www.backendurl.com/*/AuthenticationServer/</BackendURL> This setting is for defining the main url of the Authentication Backend. <br />
* <IdpURL>https://www.IDP.com/</IdpURL> The IdpURL setting is neccessary for the Client to know where you want to authenticate against.<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS --><br />
<br />
==See also==<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
* [[SYSCLS_EXTERNALAUTHCONFIG|External Auth Config Classification (SSO)]]<br />
* [[SYSCLS_EXTERNALENTITY|External Entity Classification (SSO)]]<br />
<br />
[[Category:How-To|Integrate UBIK in an SSO Environment]]<br />
[[Category:Version 3.6|Integrate UBIK in an SSO Environment]]</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22672LDAP2020-10-12T05:46:25Z<p>DST: </p>
<hr />
<div>To perform a successful authentication against an LDAP Server with UBIK, you need to create an instance of all the following classes:<br />
<br />
<br />
==LDAPLogin==<br />
The [[LDAPLogin]] object specifies a single user you want to authenticate. <br />
<br />
<br />
==LDAPGroup==<br />
The [[LDAPGroup]] specifies a group of users represented on a LDAP Server.<br />
<br />
<br />
==LDAPService==<br />
The [[LDAPService]] describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPService&diff=22659LDAPService2020-10-08T06:55:20Z<p>DST: /* Own Properties */</p>
<hr />
<div>==Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type <br />
|-<br />
| '''BaseproviderURL''' (BASEPROVIDERURL) || {{string}} <br />
|-<br />
| '''Principal''' (PRINCIPAL) || {{string}} <br />
|-<br />
| '''Credentials''' (CREDENTIALS) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
|}<br />
<br />
<br />
==BaseproviderURL==<br />
The url to a LDAP Server you want to authenticate against. A valid LDAP url looks like this: "LDAP://192.168.1.75:389"<br />
<br />
==Principal==<br />
If not defined differently, to authenticate against a LDAP Server you need a Service Account which has the rights to look up the specified LDAP Server.<br />
A valid DN belongs into the Principal property, for example: "cn=admin,dc=klu,dc=augmensys"<br />
<br />
==Credentials==<br />
The password for the Service Account.<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search of the Admin User in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22658LDAPGroup2020-10-08T06:55:04Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data Type <br />
|-<br />
| '''BaseDN''' (BASEDN) || {{string}} <br />
|-<br />
| '''GroupIdentifier''' (GROUPIDENTIFIER) || {{string}} <br />
|-<br />
| '''LDAPService''' (LDAPSERVICE) || {{guid}}<br />
|-<br />
|}<br />
<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty which needs to reference a pre defined LDAPService object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22657LDAPLogin2020-10-08T06:54:07Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type<br />
|-<br />
| '''LoginName''' (LOGINNAME) || {{string}} <br />
|-<br />
| '''Use Domain Credentials''' (USEDOMAINCREDENTIALS) || {{boolean}}<br />
|-<br />
| '''Identifier''' (IDENTIFIER) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
| '''LDAPGroup''' (LDAPGROUP) || {{guid}}<br />
|}<br />
<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22656LDAPGroup2020-10-08T06:52:18Z<p>DST: </p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data Type <br />
|-<br />
| '''BaseDN''' (BASEDN) || {{string}} <br />
|-<br />
| '''GroupIdentifier''' (GROUPIDENTIFIER) || {{string}} <br />
|-<br />
| '''LDAPService''' (LDAPSERVICE) || {{guid}}<br />
|-<br />
|}<br />
<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty which needs to reference a pre defined LDAPService object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22655LDAPLogin2020-10-08T06:52:05Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type<br />
|-<br />
| '''LoginName''' (LOGINNAME) || {{string}} <br />
|-<br />
| '''Use Domain Credentials''' (USEDOMAINCREDENTIALS) || {{boolean}}<br />
|-<br />
| '''Identifier''' (IDENTIFIER) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
| '''LDAPGroup''' (LDAPGROUP) || {{guid}}<br />
|}<br />
<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22654LDAPLogin2020-10-08T06:51:30Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type<br />
|-<br />
| '''LoginName''' (LOGINNAME) || {{string}} <br />
|-<br />
| '''Use Domain Credentials''' (USEDOMAINCREDENTIALS) || {{boolean}}<br />
|-<br />
| '''Identifier''' (IDENTIFIER) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
| '''LDAPGroup''' (LDAPGROUP) || {{reference}}<br />
|}<br />
<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22653LDAPLogin2020-10-08T06:51:16Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type<br />
|-<br />
| '''LoginName''' (LOGINNAME) || {{string}} <br />
|-<br />
| '''Use Domain Credentials''' (USEDOMAINCREDENTIALS) || {{boolean}}<br />
|-<br />
| '''Identifier''' (IDENTIFIER) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
| '''LDAPGroup''' (LDAPGROUP) || {{Reference}}<br />
|}<br />
<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22652LDAPLogin2020-10-08T06:50:50Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type<br />
|-<br />
| '''LoginName''' (LOGINNAME) || {{string}} <br />
|-<br />
| '''Use Domain Credentials''' (USEDOMAINCREDENTIALS) || {{boolean}}<br />
|-<br />
| '''Identifier''' (IDENTIFIER) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
| '''LDAPGroup''' (LDAPGROUP) || {{object}}<br />
|}<br />
<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22651LDAPLogin2020-10-08T06:50:20Z<p>DST: </p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type<br />
|-<br />
| '''LoginName''' (LOGINNAME) || {{string}} <br />
|-<br />
| '''Use Domain Credentials''' (USEDOMAINCREDENTIALS) || {{bool}}<br />
|-<br />
| '''Identifier''' (IDENTIFIER) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
| '''LDAPGroup''' (LDAPGROUP) || {{object}}<br />
|}<br />
<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22650LDAPGroup2020-10-08T06:46:01Z<p>DST: /* Own Properties */</p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data Type <br />
|-<br />
| '''BaseDN''' (BASEDN) || {{string}} <br />
|-<br />
| '''GroupIdentifier''' (GROUPIDENTIFIER) || {{string}} <br />
|-<br />
| '''LDAPService''' (LDAPSERVICE) || {{object}}<br />
|-<br />
|}<br />
<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty which needs to reference a pre defined LDAPService object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPService&diff=22649LDAPService2020-10-08T06:44:41Z<p>DST: </p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data type <br />
|-<br />
| '''BaseproviderURL''' (BASEPROVIDERURL) || {{string}} <br />
|-<br />
| '''Principal''' (PRINCIPAL) || {{string}} <br />
|-<br />
| '''Credentials''' (CREDENTIALS) || {{string}} <br />
|-<br />
| '''Searchbase''' (SEARCHBASE) || {{string}} <br />
|-<br />
|}<br />
<br />
<br />
==BaseproviderURL==<br />
The url to a LDAP Server you want to authenticate against. A valid LDAP url looks like this: "LDAP://192.168.1.75:389"<br />
<br />
==Principal==<br />
If not defined differently, to authenticate against a LDAP Server you need a Service Account which has the rights to look up the specified LDAP Server.<br />
A valid DN belongs into the Principal property, for example: "cn=admin,dc=klu,dc=augmensys"<br />
<br />
==Credentials==<br />
The password for the Service Account.<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search of the Admin User in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22648LDAPGroup2020-10-08T06:39:32Z<p>DST: </p>
<hr />
<div>== Own Properties ==<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=30% | Name !! width=20% | Data Type <br />
|-<br />
| '''BaseDN''' (BASEDN) || {{string}} <br />
|-<br />
| '''GroupIdentifier''' (GROUPIDENTIFIER) || {{string}} <br />
|-<br />
| '''LDAPService''' (LDAPSERVICE) || {{LDAPService}}<br />
|-<br />
|}<br />
<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty which needs to reference a pre defined LDAPService object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPService&diff=22647LDAPService2020-10-08T06:31:09Z<p>DST: /* LDAP Service */</p>
<hr />
<div><br />
<br />
<br />
==BaseproviderURL==<br />
The url to a LDAP Server you want to authenticate against. A valid LDAP url looks like this: "LDAP://192.168.1.75:389"<br />
<br />
==Principal==<br />
If not defined differently, to authenticate against a LDAP Server you need a Service Account which has the rights to look up the specified LDAP Server.<br />
A valid DN belongs into the Principal property, for example: "cn=admin,dc=klu,dc=augmensys"<br />
<br />
==Credentials==<br />
The password for the Service Account.<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search of the Admin User in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22646LDAPGroup2020-10-08T06:21:41Z<p>DST: /* LDAPService */</p>
<hr />
<div><br />
<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty which needs to reference a pre defined LDAPService object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22645LDAPGroup2020-10-08T06:20:43Z<p>DST: /* LDAPGroup */</p>
<hr />
<div><br />
<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty in which the belonging LDAPService object needs to get dragged in.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22644LDAPLogin2020-10-08T06:20:03Z<p>DST: /* LDAPGroup */</p>
<hr />
<div>==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty which needs to reference a pre defined LDAPGroup object.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22643LDAPLogin2020-10-08T06:17:52Z<p>DST: /* Identifier */</p>
<hr />
<div>==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. For a person, this could be an institution-wide payroll number or email address.<br />
<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty in which the belonging LDAPGroup object needs to get dragged in</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22642LDAP2020-10-08T06:08:46Z<p>DST: </p>
<hr />
<div>To perform a succesful authentication against a LDAP Server with UBIK, you need to create an instance of all the following classes:<br />
<br />
<br />
==LDAPLogin==<br />
The [[LDAPLogin]] object specifies a single user you want to authenticate. <br />
<br />
<br />
==LDAPGroup==<br />
The [[LDAPGroup]] specifies a group of users represented on a LDAP Server.<br />
<br />
<br />
==LDAPService==<br />
The [[LDAPService]] describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22632LDAP2020-09-29T12:16:18Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
<br />
==LDAPLogin==<br />
The [[LDAPLogin]] Object specifies a single User you want to authenticate. <br />
<br />
<br />
==LDAPGroup==<br />
The [[LDAPGroup]] specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
<br />
==LDAPService==<br />
The [[LDAPService]] describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22631LDAP2020-09-29T12:14:51Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
<br />
[[==LDAPLogin==]]<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
<br />
==LDAPGroup==<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
<br />
==LDAPService==<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22630LDAP2020-09-29T12:14:29Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
<br />
==LDAPLogin==<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
<br />
==LDAPGroup==<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
<br />
==LDAPService==<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22629LDAP2020-09-29T12:14:08Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
<br />
==LDAPLogin==:<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
<br />
==LDAPGroup==:<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
<br />
==LDAPService==:<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22628LDAP2020-09-29T12:13:28Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
<br />
== ''[[LDAPLogin]]'' ==:<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
<br />
== ''[[LDAPGroup]]'' ==:<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
<br />
== ''[[LDAPService]]'' ==:<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22627LDAP2020-09-29T12:12:10Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
''[[LDAPLogin]]'':<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
''[[LDAPGroup]]'':<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
''[[LDAPService]]'':<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22626LDAP2020-09-29T12:11:38Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
''[[LDAPLogin]]''<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
''[[LDAPGroup]]''<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
''[[LDAPService]]''<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22625LDAP2020-09-29T12:11:20Z<p>DST: </p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
[[LDAPLogin]]<br />
The LDAP Login Object specifies a single User you want to authenticate.<br />
<br />
[[LDAPGroup]]<br />
The LDAP Group specifies a Group of Users and where to find them on the LDAP Server.<br />
<br />
[[LDAPService]]<br />
The LDAP Service describes the actual LDAP Server and holds information about the connection to the LDAP Server and about the Service User.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22624LDAP2020-09-29T12:06:33Z<p>DST: Replaced content with "To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes: LDAPLogin LDAPGroup L..."</p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
[[LDAPLogin]]<br />
<br />
[[LDAPGroup]]<br />
<br />
[[LDAPService]]</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPService&diff=22623LDAPService2020-09-29T12:04:27Z<p>DST: Created page with "==LDAP Service== ==BaseproviderURL== The url to a LDAP Server you want to authenticate against. A valid LDAP url looks like this: "LDAP://192.168.1.75:389" ==Principal== If..."</p>
<hr />
<div>==LDAP Service==<br />
<br />
==BaseproviderURL==<br />
The url to a LDAP Server you want to authenticate against. A valid LDAP url looks like this: "LDAP://192.168.1.75:389"<br />
<br />
==Principal==<br />
If not defined differently, to authenticate against a LDAP Server you need a Service Account which has the rights to look up the specified LDAP Server.<br />
A valid DN belongs into the Principal property, for example: "cn=admin,dc=klu,dc=augmensys"<br />
<br />
==Credentials==<br />
The password for the Service Account.<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search of the Admin User in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPGroup&diff=22622LDAPGroup2020-09-29T12:04:03Z<p>DST: Created page with "==LDAPGroup== ==BaseDN== The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augm..."</p>
<hr />
<div>==LDAPGroup==<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty in which the belonging LDAPService object needs to get dragged in.</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAPLogin&diff=22621LDAPLogin2020-09-29T12:03:29Z<p>DST: Created page with "==LoginName== The name of the Login object. The name of the Login Object must be identical to the one specified on the LDAP Server. ==Use Domain Credentials== This setting mu..."</p>
<hr />
<div>==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. Example for valid Identifier: "uid","cn"...<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty in which the belonging LDAPGroup object needs to get dragged in</div>DSThttps://wikitest.augmensys.com/index.php?title=LDAP&diff=22620LDAP2020-09-29T11:53:34Z<p>DST: Created page with "To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes: LoginLDAP Object The Login Objec..."</p>
<hr />
<div>To perfrom a succesfull authentication against a LDAP Server with UBIK, you need to create an instance of each of the following Classes:<br />
<br />
<br />
[[LoginLDAP Object]]<br />
The Login Object used to authenticate against the LDAP Server<br />
<br />
==LoginName==<br />
The name of the Login object.<br />
The name of the Login Object must be identical to the one specified on the LDAP Server.<br />
<br />
==Use Domain Credentials==<br />
This setting must be set to "True" in order to perform your authentication against the LDAP Server. If set to "False" UBIK will perform it´s authentication against the internal UBIK Database.<br />
<br />
==Identifier==<br />
The Identifier property specifies a "unique identifier" for an object represented in the LDAP Directory. The domain within which the identifier is unique, and the exact semantics of the identifier, are for local definition. Example for valid Identifier: "uid","cn"...<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"<br />
<br />
==LDAPGroup==<br />
LDAPGroup is a referenceproperty in which the belonging LDAPGroup object needs to get dragged in<br />
<br />
<br />
<br />
==LDAPGroup Object==<br />
<br />
==BaseDN==<br />
The BaseDN defines the starting point for the search of users of a certain User Group. A valid BaseDN would be for example: "ou=people,dc=klu,dc=augmensys"<br />
<br />
==GroupIdentifier==<br />
The GroupIdentifier acts as a Filter and is the key element in defining the criteria used to identify entries in search requests.<br />
A valid Filter would be: "(&(objectClass=inetOrgPerson)(objectClass=top))"<br />
<br />
==LDAPService==<br />
LDAPService is a referenceproperty in which the belonging LDAPService object needs to get dragged in.<br />
<br />
<br />
<br />
[[==LDAP Service==]]<br />
<br />
==BaseproviderURL==<br />
The url to a LDAP Server you want to authenticate against. A valid LDAP url looks like this: "LDAP://192.168.1.75:389"<br />
<br />
==Principal==<br />
If not defined differently, to authenticate against a LDAP Server you need a Service Account which has the rights to look up the specified LDAP Server.<br />
A valid DN belongs into the Principal property, for example: "cn=admin,dc=klu,dc=augmensys"<br />
<br />
==Credentials==<br />
The password for the Service Account.<br />
<br />
==Searchbase==<br />
The Searchbase defines the starting point for the search of the Admin User in the directory tree. A valid Searchbase would be for example: "dc=klu,dc=augmensys"</div>DST