1
00:00:07,220 --> 00:00:16,490
First is a microsoft implementation of an identity for duration solution that uses claims based authentication.

2
00:00:17,120 --> 00:00:27,920
ADF first provides the mechanisms to implement both the identity provider and the service provider components

3
00:00:28,430 --> 00:00:30,890
in an identity for duration deployment.

4
00:00:31,640 --> 00:00:40,130
ADF first provides the following features an enterprise claims provider for claims based applications.

5
00:00:40,580 --> 00:00:49,670
You can configure an ID if a server is a claims provider, which means that the ADF server can issue

6
00:00:49,670 --> 00:00:52,610
claims about authenticated users.

7
00:00:53,240 --> 00:01:02,690
This allows an organisation to provide its users with access to claims aware applications in another

8
00:01:02,690 --> 00:01:05,720
organisation, but use them as a sole.

9
00:01:07,000 --> 00:01:13,870
Another feature is a federation service provider for identity, for duration across demands.

10
00:01:14,440 --> 00:01:25,300
This service offers federated web single sign on across domains, thereby enhancing security and reducing

11
00:01:25,300 --> 00:01:28,120
overhead for ideal administrators.

12
00:01:29,080 --> 00:01:32,290
Know some words about a fast food shows.

13
00:01:32,830 --> 00:01:36,970
The following are some of the key features of eight hour fast.

14
00:01:38,630 --> 00:01:40,400
The first feature is web.

15
00:01:40,400 --> 00:01:51,530
As so many organizations deployed 80 days after authenticate and to any day through AWOL, users can

16
00:01:51,530 --> 00:01:59,300
access all other resources that they have permission to access within the ADF.

17
00:01:59,300 --> 00:02:09,080
As far as boundaries, area affairs extends this capability to intranet or internet facing applications,

18
00:02:09,590 --> 00:02:17,720
enabling customers, partners and suppliers to have a similar streamlined user experience.

19
00:02:17,960 --> 00:02:22,670
Well, they access and organisations web based applications.

20
00:02:23,740 --> 00:02:26,500
Another feature is Web Services.

21
00:02:26,500 --> 00:02:36,010
Interoperability ADA offers is compatible with Web Services, specifications and efforts employs the

22
00:02:36,010 --> 00:02:39,040
Federation specification of W.

23
00:02:39,040 --> 00:02:43,540
S dish called w s for duration.

24
00:02:44,020 --> 00:02:52,870
W s for duration makes it possible for environments that do not use the Windows Identity Foundation

25
00:02:52,870 --> 00:03:02,860
or W RF Identity Module to federate with environments that use the Windows operating system.

26
00:03:04,110 --> 00:03:13,950
Another feature is passive and smart client support because ADA Fares is based on the S.

27
00:03:16,140 --> 00:03:24,270
Architecture, its support for degraded communications between NSW US enabled components, including

28
00:03:24,270 --> 00:03:29,190
communications between servers and passive clients such as browsers.

29
00:03:29,880 --> 00:03:41,280
IT and Windows Server 2016 allows access for soap based smart clients such as mobile phones, personal

30
00:03:41,790 --> 00:03:45,840
digital assistants and desktop apps.

31
00:03:46,940 --> 00:03:56,840
Any offense implements w s does f pr t, p, r, p and some of the w ask for duration.

32
00:03:56,840 --> 00:04:01,850
Active Request for profile standards for client support.

33
00:04:03,880 --> 00:04:04,960
Another feature.

34
00:04:06,060 --> 00:04:10,560
Is an extensible architecture.

35
00:04:11,220 --> 00:04:14,850
It first provides an extensible architecture.

36
00:04:15,940 --> 00:04:17,080
That supports.

37
00:04:18,350 --> 00:04:26,570
Various security token types, including thermal tokens and Kerberos authentication through Windows

38
00:04:26,660 --> 00:04:33,290
authentication and the ability to perform custom claims transformations.

39
00:04:33,920 --> 00:04:43,490
For example, ADF fans can convert one token type to another, or it can add custom business logic of

40
00:04:43,940 --> 00:04:47,660
the variable in an access request.

41
00:04:48,170 --> 00:04:56,960
Organizations can use this extensibility to modify their first to co-exist with their existing security

42
00:04:57,170 --> 00:05:00,080
infrastructure and business policies.

43
00:05:01,390 --> 00:05:10,120
And lastly, enhanced security at the offense also increases the security of federated solutions by

44
00:05:10,120 --> 00:05:17,920
delegating responsibility for account management to the organization closest to the user.

45
00:05:19,010 --> 00:05:28,220
Each individual organisation in the Federation continues to manage its own identities and each is capable

46
00:05:28,490 --> 00:05:36,830
of the security, enhanced sharing and accepting of identities and credentials from all the members

47
00:05:36,830 --> 00:05:37,670
resources.

48
00:05:38,910 --> 00:05:46,020
Next stop he'll be talking about what's the new in face and Windows Server 2016.