Imperva Cyber Community

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim

Hi Jim,

thanks for this link, I think it's very useful to get some practical examples.

However, I'm still stuck at the authentication phase. I created a new user in our test environment (apiuser) gave it Admin rights, logged in with that user and changed its password, and followed the example in the ZIP:

openssl enc -base64 <<< 'apiuser:APIUSERPASSWORD'
# I get for example: YXBpdXhbefahsFuZ2VtZTIK
curl -ik -X POST https://MY_MY_IP:8083/SecureSphere/api/v1/auth/session -H "Authorization: Basic YXBpdXhbefahsFuZ2VtZTIK"

But the answer is always:
HTTP/1.1 401 Unauthorized
Set-Cookie: JSESSIONID=7FDBCB1602EF6F865EF3CF4106167482; Path=/SecureSphere; Secure; HttpOnly
Content-Security-Policy: frame-ancestors 'self'
WWW-Authenticate: Basic realm="Open API"
Secsph-Request-Id: 294814241117554424
Content-Length: 71
Date: Thu, 20 Aug 2020 14:33:38 GMT
Server: NA

{"errors":[{"error-code":"IMP-10063","description":"Bad credentials"}]}

Am I missing something? Should I create the user in another way?

Thank you!
Fabio

Also, if you are pulling the information from an external repository like LDAP, you can look at our Data Enrichment policies to avoid the API completely.

Jim