summaryrefslogtreecommitdiff
path: root/t/features/bind.feature
blob: 74b19be36248853ff02f3f9f81b6176e3640fa42 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Feature: Binding to the directory
 As a directory consumer
 I want to ensure that I can bind properly to directories
 In order to establish my identity

 Background:
   Given a usable Net::LDAPapi class

 Scenario: Can bind anonymously
   Given a Net::LDAPapi object that has been connected to the LDAP server
   When I've bound with anonymous authentication to the directory
   Then the bind result is LDAP_SUCCESS

 Scenario: Can bind with simple authentication
   Given a Net::LDAPapi object that has been connected to the LDAP server
   When I've bound with simple authentication to the directory
   Then the bind result is LDAP_SUCCESS

 Scenario: Can bind with sasl authentication
   Given a Net::LDAPapi object that has been connected to the ldapi LDAP server
   When I've bound with sasl authentication to the directory
   Then the bind result is LDAP_SUCCESS

 Scenario: Can asynchronously bind anonymously
   Given a Net::LDAPapi object that has been connected to the LDAP server
   When I've asynchronously bound with anonymous authentication to the directory
   Then the bind result message type is LDAP_RES_BIND
   And the bind result is LDAP_SUCCESS

 Scenario: Can asynchronously bind with simple authentication
   Given a Net::LDAPapi object that has been connected to the LDAP server
   When I've asynchronously bound with simple authentication to the directory
   Then the bind result message type is LDAP_RES_BIND
   And the bind result is LDAP_SUCCESS

# Scenario: Can asynchronously bind with sasl authentication
#   Given a Net::LDAPapi object that has been connected to the ldapi LDAP server
#   When I've asynchronously bound with sasl authentication to the directory
#   Then the bind result message type is LDAP_RES_BIND
#   And the bind result is LDAP_SUCCESS