Issue #4259: User can not disable his own tokens (aci issue) - freeipa

freeipa

#4259 User can not disable his own tokens (aci issue)

Closed: Fixed None Opened 10 years ago by pvoborni.

User can delete his tokens but can't disable them.

Assuming there would be at least one enabled left.

Cause:

Insufficient access: Insufficient 'write' privilege to the 'ipatokenDisabled' attribute of entry 'ipatokenuniqueid=99aa4c75-36b8-4c20-b553-eecfc47aed98,cn=otp,dc=idm,dc=obfuscated'.

mkosek commented 10 years ago

This ticket is not complete yet, moving to next month milestone.

npmccallum commented 9 years ago

I'm not sure we actually want users to enable/disable their own tokens. Is there a use case for this?

npmccallum commented 9 years ago

http://www.redhat.com/archives/freeipa-devel/2014-May/msg00073.html

mkosek commented 9 years ago

master:

9885125 Add support for managedBy to tokens

Metadata Update from @pvoborni:
- Issue assigned to npmccallum
- Issue set to the milestone: FreeIPA 4.0 - 2014/06

7 years ago

Metadata

Assignee

npmccallum

Tags

None

Blocking

None

Depending on

None

Priority

normal

Milestone

FreeIPA 4.0 - 2014/06

None

affects_doc

None

source

None

knownissue

None

type

defect

blockedby

None

test_case

None

component

OTP

blocking

None

on_review

keywords

None

test_coverage

None

reviewer

jcholast

external_tracker

None

rhbz

tester

None

changelog

None

design

None

freeipa

Source Code

#4259 User can not disable his own tokens (aci issue) Closed: Fixed None Opened 10 years ago by pvoborni.

Metadata

#4259 User can not disable his own tokens (aci issue)

Closed: Fixed None Opened 10 years ago by pvoborni.