New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set username/tenantname differently for BASIC authentication #57

Closed
robert-bor opened this Issue Mar 27, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@robert-bor
Member

robert-bor commented Mar 27, 2014

Currently, the username/tenantname (which are passed as "username:tenantname") are set with setUsername.

This must be settable with:

  • setUsername
  • setTenantName

JOSS must take care of appending the two variables into a single statement.

@robert-bor robert-bor added the bug label Mar 27, 2014

@robert-bor robert-bor added this to the 0.9.5 milestone Mar 27, 2014

@robert-bor robert-bor self-assigned this Mar 27, 2014

robert-bor added a commit that referenced this issue Mar 29, 2014

Issue #57 BASIC / TEMPAUTH authentication will set the username as fo…
…llows. If only username is passed, use just this. If username and tenant are both passed, use them both, separated by a colon
@robert-bor

This comment has been minimized.

Show comment
Hide comment
@robert-bor

robert-bor Mar 29, 2014

Member

If username and tenantName are both passed, they will be used as the user to pass, separated by a colon. This functionality will be part of v0.9.5

Member

robert-bor commented Mar 29, 2014

If username and tenantName are both passed, they will be used as the user to pass, separated by a colon. This functionality will be part of v0.9.5

@robert-bor robert-bor closed this Mar 29, 2014

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

Issue #57 BASIC / TEMPAUTH authentication will set the username as fo…
…llows. If only username is passed, use just this. If username and tenant are both passed, use them both, separated by a colon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment