You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/kerberos.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -213,7 +213,7 @@ In most cases, knowing detailed steps in depth isn't necessary for day-to-day ad
213
213
#### Detailed steps
214
214
215
215
<details>
216
-
<summary>For detailed steps about how an SMB machine account is created in Azure NetApp Files, expand the list below.</summary>
216
+
<summary>For detailed steps about how an SMB machine account is created in Azure NetApp Files, expand the list.</summary>
217
217
218
218
- DNS lookup is performed using the DNS configuration for the SRV record of a Kerberos KDC. Azure NetApp Files uses the following SRV records in its requests.
219
219
-`_kerberos._tcp.dc._msdcs.CONTOSO.COM`
@@ -360,7 +360,7 @@ If a DNS A/AAAA record is created (for instance, AZURE-FILESHARE.contoso.com) an
360
360
361
361
### Supported SMB server capabilities in Azure NetApp Files
362
362
363
-
When the SMB "negotiate protocol" request is made, the Azure NetApp Files SMB server is queried for support of specific capabilities. The table below shows the capabilities queried and the response returned from an Azure NetApp Files SMB volume when a [Session Setup/Tree connect](#smb-share-connection-workflow-kerberos) is performed.
363
+
When the SMB "negotiate protocol" request is made, the Azure NetApp Files SMB server is queried for support of specific capabilities. The following table shows the capabilities queried and the response returned from an Azure NetApp Files SMB volume when a [Session Setup/Tree connect](#smb-share-connection-workflow-kerberos) is performed.
364
364
365
365
| SMB capability | Supported by Azure NetApp Files? |
366
366
| - | - |
@@ -374,7 +374,7 @@ When the SMB "negotiate protocol" request is made, the Azure NetApp Files SMB se
374
374
375
375
### Supported SMB share capabilities and properties in Azure NetApp Files
376
376
377
-
During SMB share access, a "tree connect" request is performed and the supported SMB share capabilities and properties are queried by the client to the Azure NetApp Files server. The table below shows the share capabilities queried and the response returned from an Azure NetApp Files SMB volume as seen in a packet capture.
377
+
During SMB share access, a "tree connect" request is performed and the supported SMB share capabilities and properties are queried by the client to the Azure NetApp Files server. The following table shows the share capabilities queried and the response returned from an Azure NetApp Files SMB volume as seen in a packet capture.
@@ -406,7 +406,7 @@ The following table displays the share properties queried and the response retur
406
406
407
407
## How NFS Kerberos works in Azure NetApp Files
408
408
409
-
NFS Kerberos works separately from SMB services, as the machine accounts created for each protocol can't share keytabs because of the potential for changes to the Key Version Number (kvno) in one keytab impacting the other service. As a result, the workflows for SMB services for Kerberos and NFS for Kerberos differ in functionality in some areas.
409
+
NFS Kerberos works separately from SMB services, as the machine accounts created for each protocol can't share keytabs because of the potential for changes to the Key Version Number (`kvno`) in one keytab impacting the other service. As a result, the workflows for SMB services for Kerberos and NFS for Kerberos differ in functionality in some areas.
410
410
411
411
### Initial configuration of Kerberos realm
412
412
@@ -461,7 +461,7 @@ The following diagram shows how an NFS SPN is created when an Azure NetApp Files
<summary>For detailed steps about how an NFS Kerberos SPN is created with Azure NetApp Files, expand the list below.</summary>
464
+
<summary>For detailed steps about how an NFS Kerberos SPN is created with Azure NetApp Files, expand the list.</summary>
465
465
466
466
- Admin credentials passed to KDC specified in the realm configuration using the username provided for use in the Active Directory connection – user must have permission to view/create objects in the specified OU.
467
467
- The DNS servers specified in the Azure NetApp Files Active Directory connection configuration are queried by Azure NetApp Files for the Kerberos service records (SRV) in the following formats:
0 commit comments