Overview#
Server requires a context to be of value.In most of our conditions, a Protocol Server is probably the best general definition.!! Client-server Server are the Provider of services (Protocol Server) to a Consumer of services (Protocol Client)ObjectClass Definition#
The ObjectClass Type is defined as:- OID: 2.16.840.1.113719.1.1.6.1.22
- NAME: Server
- SUP: top
- ABSTRACT
- MUST:
- MAY:
- Extended Flags:
- X-NDS_NAMING 'cn'
- X-NDS_CONTAINMENT ( 'Organization' 'organizationalUnit' 'domain' )
- X-NDS_NOT_CONTAINER '1'
- X-NDS_NONREMOVABLE '1'
More Information#
There might be more information for this subject on one of the following:- 2.16.840.1.113719.1.1.4.1.1
- 2.16.840.1.113719.1.1.4.1.112
- 2.16.840.1.113719.1.1.4.1.165
- 2.16.840.1.113719.1.1.4.1.27
- 2.16.840.1.113719.1.1.4.1.4
- 2.16.840.1.113719.1.1.4.1.529
- 2.16.840.1.113719.1.1.4.1.538
- 2.16.840.1.113719.1.1.4.1.54
- 2.16.840.1.113719.1.1.4.1.82
- 2.16.840.1.113719.1.1.4.1.84
- 2.16.840.1.113719.1.1.4.1.89
- 2.16.840.1.113719.1.1.4.1.92
- 2.16.840.1.113719.1.1.4.1.95
- 2.16.840.1.113719.1.1.4.1.98
- 2.16.840.1.113719.1.1.6.1.0
- 2.16.840.1.113719.1.1.6.1.18
- 2.16.840.1.113719.1.1.6.1.20
- 2.16.840.1.113719.1.1.6.1.22
- 2.16.840.1.113719.1.1.6.1.27
- 2.16.840.1.113719.1.1.6.1.31
- 2.16.840.1.113719.1.1.6.1.4
- 2.16.840.1.113719.1.4.2.1.0
- 2.16.840.1.113719.1.4.2.1.1
- 2.16.840.1.113719.1.4.4.0.1
- 2.16.840.1.113719.1.4.4.0.2
- 2.16.840.1.113719.1.51.6.1.2
- 2.5.4.10
- 2.5.4.3
- 2.5.4.34
- AP_REQ
- AWS Elastic File System
- Authenticated Protected Channel
- Authorization Header
- Basic Authentication Scheme
- Best Practices Password
- Binding
- Bot
- CONTROL-SA
- CTAP2
- Certificate Pinning
- Certificate Renewal
- Challenge-Handshake Authentication Protocol
- Channel Binding
- Channel Bindings for TLS
- Cipher_suites
- Client-server
- ClientHello
- Clients
- Cloud Native
- Cloud computing
- Cn
- Configuration Management
- Content-Type
- Cookie
- CredSSP
- DNS-Based Authentication of Named Entities
- DSE_AUTHENTICATE
- Description
- Domain Name server
- DomainKeys Identified Mail
- Durability
- ESTABLISHED
- Ephemeral Device
- Extended Protection for Authentication
- Fetch API
- Forbidden
- FullName
- Global Catalog
- GraphQL
- HTTP
- HTTP 101
- HTTP 400
- HTTP 403
- HTTP 407
- HTTP 410
- HTTP Cache Directive
- HTTP Request
- HTTP Status Code
- HTTP-Server
- HelloRetryRequest
- How SSL-TLS Works
- Hypermedia As The Engine Of Application State
- Hypertext Transfer Protocol
- INVALID_RESPONSE
- Impersonation Token
- Implicit Grant
- Infrastructure As Code
- Infrastructure as a Service
- Instant Messaging
- Inter-Process Communication
- Internet Relay Chat
- JWK Set
- Java KeyStore
- Kerberos Cryptosystem Negotiation Extension
- Key server
- KeyShare
- Keytool
- LAN Manager authentication level
- LDAP Result Codes
- LDAP Signing
- LDAP_ADMINLIMIT_EXCEEDED
- LDAP_CONTROL_NOT_FOUND
- LISTEN
- LdapStdCompliance
- LoRaWAN
- Local device
- Mainframe
- Malfeasance
- ManagedBy
- Mutual Authentication
- NDS Authentication
- NGINX
- NMAS Result Codes
- NTDSDSA
- NcpServer
- Netlogon attribute
- NetworkAddress
- Novell INC
- ObjectClass-Names
- Opaque token
- Openid-configuration
- Opportunistic TLS
- Ou
- Password Storage Scheme
- Password-authenticated Key Exchange
- Point-of-Presence
- Policy Based Management System
- Privileged User Management
- Protocol Server
- Protocol ossification
- Proxy
- Proxy Server
- Recipient
- Recursive name server
- Remote Authentication Dial-In User Service
- Remote Procedure Call
- Resource Inventory Service
- Result Code
- Rich Communication Services
- SASDFM key
- SASL
- SASL EXTERNAL
- SECURITY_IMPERSONATION_LEVEL
- SNTP
- SSL Handshake Failed
- SSL-TLS Interception
- SYN-ACK
- SYN-RECEIVED
- SYN-SENT
- Security Domain Infrastructure
- Security Information and Event Management
- Server Storage Key
- Server-side
- ServerHello
- Serverless
- Service Account
- Session Key
- SessionData
- Sharding
- Simple Network Time Protocol
- Single-Page Application
- Socket Secure
- Stateless
- Strict-Transport-Security
- Supported_versions
- TIME-WAIT
- TLS Client Authentication
- TLSA
- Telegram
- Terminology for Constrained-Node Networks
- Time synchronization
- Timezone
- Token Binding Protocol
- Token Binding over HTTP
- Transmission Control Protocol
- Transport Layer Security
- Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation
- URI Fragment Identifiers
- Universal Authentication Framework
- User and Entity Behavior Analytics
- User-agent
- Version Control System
- Why Use Tokens
- Windows Authentication Package
- Windows NT
- Windows Server
- XMLHttpRequest
- Zero Trust
- Zero-configuration networking
- groupwisepostoffice-oid
- netsvc-oid
- svcinfo-oid
- svctype-oid
- svctypeid-oid