--- /dev/null
+*** Settings ***
+Documentation Test suite: Authentication Support for Keystone
+...
+... This feature implements the user management for ODL NBI REST APIs integrated with OpenStack, so that the authentication functionality provided by Keystone can be used. This allows consuming ODL NBI REST APIs using the same authentication procedures as any OpenStack project, such as Nova, Neutron, etc. bringing the benefits of a centralized / unified user management framework.
+...
+... As a first step, It shall be possible to authenticate users against Keystone by using passwords provided by the users.
+Suite Setup Init Suite
+Suite Teardown Cleanup Suite
+Test Timeout
+Library SSHLibrary
+Library Collections
+Library OperatingSystem
+Library RequestsLibrary
+Resource ../../../libraries/Utils.robot
+Resource ../../../libraries/TemplatedRequests.robot
+Resource ../../../libraries/KarafKeywords.robot
+Resource ../../../libraries/ClusterManagement.robot
+Resource ../../../variables/Variables.robot
+Resource ../../../libraries/AAA/DockerKeystone.robot
+
+*** Variables ***
+
+*** Test Cases ***
+Successful Authentication Including Domain
+ [Documentation] *Test Case: Successful Authentication with user@domain/password credentials*
+ ...
+ ... Steps:
+ ...
+ ... - Create an HTTP session with ODL as "sdnadmin" user in "sdn" domain
+ ... - Check that the access to URLs of ODL NBI is allowed \ because "sdnadmin" user is associated to domain "sdn" in Keystone and the provided password is the right one
+ [Tags]
+ Create Session session http://${ODL_SYSTEM_IP}:${RESTCONFPORT} auth=${AUTH_SDN_DOMAIN} headers=${HEADERS}
+ ${resp}= RequestsLibrary.Post Request session /restconf/operations/aaa-cert-rpc:getODLCertificate headers=${HEADERS}
+ Log ${resp}\n${resp.headers}\n${resp.content}
+ Should Contain ${ALLOWED_STATUS_CODES} ${resp.status_code}
+
+Successful Authentication Without Domain
+ [Documentation] *Test Case: Successful Authentication with user/password credentials. No domain included*
+ ...
+ ... Steps:
+ ...
+ ... - Create an HTTP session with ODL as "CSC_user" user without specifying any domain then domain "Default" is considered
+ ... - Check that the access to URLs of ODL NBI is allowed because "CSC_user" user is associated to domain "Default" in Keystone and the provided password is the right one
+ [Tags] include
+ Create Session session http://${ODL_SYSTEM_IP}:${RESTCONFPORT} auth=${AUTH_CSC_SDN} headers=${HEADERS}
+ ${resp}= RequestsLibrary.Post Request session /restconf/operations/aaa-cert-rpc:getODLCertificate headers=${HEADERS}
+ Log ${resp}\n${resp.headers}\n${resp.content}
+ Should Contain ${ALLOWED_STATUS_CODES} ${resp.status_code}
+
+Unsuccessful Authentication Wrong User
+ [Documentation] *Test Case: UnSuccessful Authentication with worng user/password credentials*
+ ...
+ ... Steps:
+ ...
+ ... - Create an HTTP session with ODL as an invalid user
+ ... - Check that the access to URLs of ODL NBI is NOT allowed \ because "invaliduser" user does not exist in Keystone
+ [Tags]
+ Create Session session http://${ODL_SYSTEM_IP}:${RESTCONFPORT} auth=${AUTH_INVALID} headers=${HEADERS}
+ ${resp}= RequestsLibrary.Post Request session /restconf/operations/aaa-cert-rpc:getODLCertificate headers=${HEADERS}
+ Log ${resp}
+ Log ${resp.headers}
+ Log ${resp.content}
+ Should Contain ${UNAUTHORIZED_STATUS_CODES} ${resp.status_code}
+
+UnSuccessful Authentication Without Domain
+ [Documentation] *Test Case: UnSuccessful Authentication without domain*
+ ...
+ ... Steps:
+ ...
+ ...
+ ... - Create an HTTP session with ODL as "sdnadmin" user without specifying any domain then domain "Default" is considered
+ ... - Check that the access to URLs of ODL NBI is NOT allowed because "sdnadmin" user is not associated to domain "Default" in Keystone but to "sdn" which is not included in the credentials
+ [Tags]
+ Create Session session http://${ODL_SYSTEM_IP}:${RESTCONFPORT} auth=${AUTH_SDN} headers=${HEADERS}
+ ${resp}= RequestsLibrary.Post Request session /restconf/operations/aaa-cert-rpc:getODLCertificate headers=${HEADERS}
+ Log ${resp}
+ Log ${resp.headers}
+ Log ${resp.content}
+ Should Contain ${UNAUTHORIZED_STATUS_CODES} ${resp.status_code}
+
+Unsuccessful Authentication Wrong Domain
+ [Documentation] *Test Case: UnSuccessful Authentication with wrong domain*
+ ...
+ ... Steps:
+ ...
+ ... Steps:
+ ...
+ ... - Create an HTTP session with ODL as "sdnadmin" user with "wrong" as domain
+ ... - Check that the access to URLs of ODL NBI is NOT allowed because "sdnadmin" user is not associated to domain "wrong" in Keystone but to "sdn"
+ ...
+ ... Note: Also for troubleshooting purposes keystone debug files are dumped
+ [Tags]
+ Create Session session http://${ODL_SYSTEM_IP}:${RESTCONFPORT} auth=${AUTH_SDN_WRONG_DOM} headers=${HEADERS}
+ ${resp}= RequestsLibrary.Post Request session /restconf/operations/aaa-cert-rpc:getODLCertificate headers=${HEADERS}
+ Log ${resp}
+ Log ${resp.headers}
+ Log ${resp.content}
+ ${output} SSHLibrary.Execute Command docker exec -t keystone bash -c "cat /var/log/nginx-access.log"
+ Log ${output}
+ ${output} SSHLibrary.Execute Command docker exec -t keystone bash -c "cat /var/log/uwsgi-keystone-admin.log"
+ Log ${output}
+ ${output} SSHLibrary.Execute Command docker exec -t keystone bash -c "cat /var/log/nginx-error.log"
+ Log ${output}
+ ${output} SSHLibrary.Execute Command docker exec -t keystone bash -c "cat /var/log/uwsgi-keystone-public.log"
+ Log ${output}
+ Should Contain ${UNAUTHORIZED_STATUS_CODES} ${resp.status_code}
+
+*** Keywords ***
+Init Suite
+ [Documentation] The steps included in the Initialization phase are:
+ ...
+ ... - Run Docker Keystone: Deploy a container in the SYSTEM TOOL node containing the Keystone
+ ...
+ ... - Configure AAA in Controller: shiro.ini file is modified to add new authentication realm based on Keystone
+ ...
+ ... - Restart Controller: This restart is needed in order to activate new shiro.ini configuration
+ ...
+ ... - Provision Keystone: Populate keystone database with the needed users and roles
+ ...
+ ... - Install Keystone certificate into ODL so that the protocol used in the ODL-Keystone communication is HTTPS with server certificate authentication
+ ${TOOLS_SYSTEM_NAME} Run Command On Remote System ${TOOLS_SYSTEM_IP} hostname -f user=${TOOLS_SYSTEM_USER} password=${TOOLS_SYSTEM_PASSWORD}
+ Run Docker Keystone
+ Configure AAA In Controller ${TOOLS_SYSTEM_NAME}
+ Restart Controller
+ Provision Keystone
+ Set Suite Variable ${PUT_KEYSTONE_CERT_FILE} ${CURDIR}/../../../variables/aaa/put-keystone-cert.json
+ Set Keystone Certificate into ODL ${PUT_KEYSTONE_CERT_FILE} ${TOOLS_SYSTEM_NAME}
+
+Cleanup Suite
+ [Documentation] Destoy keystone container
+ Set Domain To False ${domain} ${HEADERS_TOKEN}
+ Delete Keystone Domain ${domain} ${HEADERS_TOKEN}
+ Destroy Docker Keystone
+
+Configure AAA In Controller
+ [Arguments] ${TOOLS_SYSTEM_NAME}
+ [Documentation] With this keyword shiro.ini and aaa-cert-config.xml are modified to configure Keystone Authentication Realm using TLS1.2. Here you have the settings:
+ ...
+ ... - shiro.ini:
+ ...
+ ... keystoneAuthRealm = org.opendaylight.aaa.shiro.realm.KeystoneAuthRealm
+ ... keystoneAuthRealm.url = https://sandbox-29591-30-docker-0:35357
+ ... keystoneAuthRealm.sslVerification = true
+ ...
+ ... securityManager.realms = $tokenAuthRealm, $keystoneAuthRealm
+ ...
+ ...
+ ...
+ ...
+ ... - aaa-cert-config.xml:
+ ... <use-config>true</use-config>
+ ...
+ ... <tls-protocols>TLSv1.2</tls-protocols>
+ ${shiro_path} Run Command On Controller cmd=cd /;find /|grep shiro.ini|grep etc|grep -v denied
+ ${cert_path} Run Command On Controller cmd=cd /;find /|grep aaa-cert-config.xml|grep etc|grep -v denied
+ ${result} Run Command On Controller cmd=sed -ie 's/#keystoneAuthRealm =.*/keystoneAuthRealm = org.opendaylight.aaa.shiro.realm.KeystoneAuthRealm/g' ${shiro_path}
+ ${result} Run Command On Controller cmd=sed -ie 's/#keystoneAuthRealm.url =.*/keystoneAuthRealm.url = https:\\/\\/${TOOLS_SYSTEM_NAME}:35357/g' ${shiro_path}
+ ${result} Run Command On Controller cmd=sed -ie 's/securityManager.realms =.*/securityManager.realms = $tokenAuthRealm, $keystoneAuthRealm/g' ${shiro_path}
+ ${result} Run Command On Controller cmd=sed -ie 's/#keystoneAuthRealm.sslVerification =.*/keystoneAuthRealm.sslVerification = true/g' ${shiro_path}
+ ${result} Run Command On Controller cmd=sed -ie '/^\\/operations\\/aaa-cert-rpc/d' ${shiro_path}
+ ${result} Run Command On Controller cmd=sed -ie 's/<use-config>.*/<use-config>true<\\/use-config>/g' ${cert_path}
+ ${result} Run Command On Controller cmd=sed -ie 's/<tls-protocols.*/<tls-protocols>TLSv1.2<\\/tls-protocols>/g' ${cert_path}
+ ${result} Run Command On Controller cmd=cat ${shiro_path}
+ Log ${result}
+ ${result} Run Command On Controller cmd=cat ${cert_path}
+ Log ${result}
+ ${result} Run Command On Controller cmd=sudo sed -i "2i${TOOLS_SYSTEM_IP} \ \ ${TOOLS_SYSTEM_NAME}" /etc/hosts
+ ${result} Run Command On Controller cmd=cat /etc/hosts
+ Log ${result}
+
+Provision Keystone
+ [Documentation] As CSC_user provision:
+ ... - Domain "sdn"
+ ... - User "sdnadmin"
+ ... - Role "admin" to "sdnadmin" user in "sdn" domain
+ ${result} Create Keystone session ${TOOLS_SYSTEM_IP}
+ Log ${result}
+ Set Suite Variable ${CREATE_TOKEN_FILE} ${CURDIR}/../../../variables/aaa/create-token.json
+ ${token} Get Keystone Token ${TOOLS_SYSTEM_IP} ${CREATE_TOKEN_FILE}
+ Log ${HEADERS}
+ &{HEADERS} Create Dictionary X-Auth-Token=${token} Content-Type=application/json
+ Set Suite Variable ${HEADERS_TOKEN} ${HEADERS}
+ ${admin_role_id} Get Admin Role Id ${HEADERS_TOKEN}
+ Set Suite Variable ${CREATE_DOMAIN_FILE} ${CURDIR}/../../../variables/aaa/create-domain.json
+ ${domain_local} Create Keystone Domain ${HEADERS_TOKEN} ${CREATE_DOMAIN_FILE}
+ Set Suite Variable ${domain} ${domain_local}
+ Set Suite Variable ${CREATE_USERS_FILE} ${CURDIR}/../../../variables/aaa/create-user.json
+ ${normalized_file}= OperatingSystem.Normalize Path ${CREATE_USERS_FILE}
+ ${output} OperatingSystem.Run sed -i 's/\"domain_id\".*/\"domain_id\"\: \"${domain}\",/g' ${CREATE_USERS_FILE}
+ ${user} Create Keystone User in a Domain ${HEADERS_TOKEN} ${CREATE_USERS_FILE}
+ Grant Admin Role ${domain} ${user} ${admin_role_id} ${HEADERS_TOKEN}
+
+Restart Controller
+ [Documentation] Controller restart is needed in order the new shiro.ini config takes effect
+ ClusterManagement.ClusterManagement_Setup
+ Wait Until Keyword Succeeds 5x 20 Stop_Single_Member 1
+ Start_Single_Member 1 wait_for_sync=False timeout=120
+ Wait Until Keyword Succeeds 30x 5s Get Controller Modules
+
+Get Controller Modules
+ [Documentation] Get the restconf modules, check 200 status and ietf-restconf presence
+ Create Session session1 http://${ODL_SYSTEM_IP}:${RESTCONFPORT} auth=${AUTH} headers=${HEADERS}
+ ${resp} = RequestsLibrary.Get_Request session1 ${MODULES_API}
+ BuiltIn.Log ${resp.content}
+ BuiltIn.Should_Be_Equal ${resp.status_code} ${200}
+ BuiltIn.Should_Contain ${resp.content} ietf-restconf
Code Review / integration / test.git / blobdiff