Security
Token
There is no security token.
Firewall
main
Name
Security enabled
Stateless
Configuration
Key | Value |
---|---|
provider | security.user.provider.concrete.app_user_provider |
context | main |
entry_point | App\Security\KbinAuthenticator |
user_checker | App\Security\UserChecker |
access_denied_handler | (none) |
access_denied_url | (none) |
authenticators | [ "two_factor" "remember_me" "App\Security\KbinAuthenticator" "App\Security\FacebookAuthenticator" "App\Security\GoogleAuthenticator" "App\Security\GithubAuthenticator" "App\Security\KeycloakAuthenticator" ] |
Listeners
Listener | Duration | Response |
---|---|---|
Symfony\Component\Security\Http\Firewall\ChannelListener {#723 -map: Symfony\Component\Security\Http\AccessMap {#722 …} -logger: Monolog\Logger {#783 …} -httpPort: 80 -httpsPort: 443 } |
0.00 ms | (none) |
Symfony\Component\Security\Http\Firewall\ContextListener {#706 -tokenStorage: Symfony\Component\Security\Core\Authentication\Token\Storage\TokenStorage {#1017 …} -sessionKey: "_security_main" -logger: Monolog\Logger {#783 …} -userProviders: Symfony\Component\DependencyInjection\Argument\RewindableGenerator {#705 …} -dispatcher: Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher {#747 …} -registered: false -trustResolver: Scheb\TwoFactorBundle\Security\Authentication\AuthenticationTrustResolver {#780 …} -sessionTrackerEnabler: Symfony\Component\Security\Core\Authentication\Token\Storage\UsageTrackingTokenStorage::enableUsageTracking(): void {#703 …} } |
1.43 ms | (none) |
Symfony\Component\Security\Http\Firewall\AuthenticatorManagerListener {#584 -authenticatorManager: Symfony\Component\Security\Http\Authentication\AuthenticatorManager {#595 …} } |
0.00 ms | (none) |
Scheb\TwoFactorBundle\Security\Http\Firewall\TwoFactorAccessListener {#582 -twoFactorFirewallConfig: Scheb\TwoFactorBundle\Security\TwoFactor\TwoFactorFirewallConfig {#842 …} -tokenStorage: Symfony\Component\Security\Core\Authentication\Token\Storage\UsageTrackingTokenStorage {#1018 …} -twoFactorAccessDecider: Scheb\TwoFactorBundle\Security\Authorization\TwoFactorAccessDecider {#581 …} } |
0.15 ms | (none) |
Symfony\Component\Security\Http\Firewall\AccessListener {#579 -tokenStorage: Symfony\Component\Security\Core\Authentication\Token\Storage\UsageTrackingTokenStorage {#1018 …} -accessDecisionManager: Symfony\Component\Security\Core\Authorization\TraceableAccessDecisionManager {#937 …} -map: Symfony\Component\Security\Http\AccessMap {#722 …} } |
0.00 ms | (none) |
Symfony\Component\Security\Http\Firewall\LogoutListener {#786 -tokenStorage: Symfony\Component\Security\Core\Authentication\Token\Storage\UsageTrackingTokenStorage {#1018 …} -options: [ "csrf_parameter" => "_csrf_token" "csrf_token_id" => "logout" "logout_path" => "app_logout" ] -httpUtils: Symfony\Component\Security\Http\HttpUtils {#841 …} -csrfTokenManager: Symfony\Component\Security\Csrf\CsrfTokenManager {#1015 …} -eventDispatcher: Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher {#747 …} } |
0.00 ms | (none) |
Authenticators
No authenticators have been recorded. Check previous profiles on your authentication endpoint.
Access Decision
affirmative
Strategy
Access decision log
# | Result | Attributes | Object | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | DENIED | ROLE_USER | null |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
2 | DENIED | moderate | App\Entity\Entry {#2363 +user: App\Entity\User {#265 …} +magazine: Proxies\__CG__\App\Entity\Magazine {#2377 …} +image: null +domain: Proxies\__CG__\App\Entity\Domain {#2370 …} +slug: "Question-about-modlog-entities-in-the-Lemmy-API" +title: "Question about modlog entities in the Lemmy API" +url: null +body: """ Hi, I’m working on modlog display for the Voyager client and I have a quick question regarding mod log item views, specifically, the `ModBanView` ([join-lemmy.org/api/interfaces/ModBanView.html](https://join-lemmy.org/api/interfaces/ModBanView.html)).\n \n If instance bans require admin rights, why is the person issuing the ban called “moderator” here?\n \n Same goes for some other items like `ModAddView` and `ModAddCommunityView`. Meanwhile, `ModHideCommunity` view uses “admin” instead.\n \n Unfortunately, there is no explanation in the API docs to help explain this apparent inconsistency. Can anyone help shed some light on this? """ +type: "article" +lang: "en" +isOc: false +hasEmbed: false +commentCount: 2 +favouriteCount: 3 +score: 0 +isAdult: false +sticky: false +lastActive: DateTime @1711238280 {#2454 : 2024-03-24 00:58:00.0 +01:00 } +ip: null +adaAmount: 0 +tags: null +mentions: null +comments: Doctrine\ORM\PersistentCollection {#2469 …} +votes: Doctrine\ORM\PersistentCollection {#2467 …} +reports: Doctrine\ORM\PersistentCollection {#2372 …} +favourites: Doctrine\ORM\PersistentCollection {#2386 …} +notifications: Doctrine\ORM\PersistentCollection {#2385 …} +badges: Doctrine\ORM\PersistentCollection {#2378 …} +children: [] -id: 26561 -titleTs: "'api':8 'entiti':4 'lemmi':7 'modlog':3 'question':1" -bodyTs: "'/api/interfaces/modbanview.html](https://join-lemmy.org/api/interfaces/modbanview.html)).':28 'admin':33,59 'anyon':77 'api':68 'appar':74 'ban':31,41 'call':42 'client':11 'display':7 'doc':69 'explain':72 'explan':65 'goe':46 'help':71,78 'hi':1 'inconsist':75 'instanc':30 'instead':60 'issu':39 'item':21,50 'join-lemmy.org':27 'join-lemmy.org/api/interfaces/modbanview.html](https://join-lemmy.org/api/interfaces/modbanview.html)).':26 'light':81 'like':51 'log':20 'm':3 'meanwhil':55 'mod':19 'modaddcommunityview':54 'modaddview':52 'modbanview':25 'moder':43 'modhidecommun':56 'modlog':6 'person':38 'question':17 'quick':16 'regard':18 'requir':32 'right':34 'shed':79 'specif':23 'unfortun':61 'use':58 'view':22,57 'voyag':10 'work':4" +cross: false +upVotes: 0 +downVotes: 0 +ranking: 1704072878 +visibility: "visible " +apId: "https://lemmy.today/post/4732610" +editedAt: null +createdAt: DateTimeImmutable @1704055378 {#2453 : 2023-12-31 21:42:58.0 +01:00 } } |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
3 | DENIED | edit | App\Entity\Entry {#2363 +user: App\Entity\User {#265 …} +magazine: Proxies\__CG__\App\Entity\Magazine {#2377 …} +image: null +domain: Proxies\__CG__\App\Entity\Domain {#2370 …} +slug: "Question-about-modlog-entities-in-the-Lemmy-API" +title: "Question about modlog entities in the Lemmy API" +url: null +body: """ Hi, I’m working on modlog display for the Voyager client and I have a quick question regarding mod log item views, specifically, the `ModBanView` ([join-lemmy.org/api/interfaces/ModBanView.html](https://join-lemmy.org/api/interfaces/ModBanView.html)).\n \n If instance bans require admin rights, why is the person issuing the ban called “moderator” here?\n \n Same goes for some other items like `ModAddView` and `ModAddCommunityView`. Meanwhile, `ModHideCommunity` view uses “admin” instead.\n \n Unfortunately, there is no explanation in the API docs to help explain this apparent inconsistency. Can anyone help shed some light on this? """ +type: "article" +lang: "en" +isOc: false +hasEmbed: false +commentCount: 2 +favouriteCount: 3 +score: 0 +isAdult: false +sticky: false +lastActive: DateTime @1711238280 {#2454 : 2024-03-24 00:58:00.0 +01:00 } +ip: null +adaAmount: 0 +tags: null +mentions: null +comments: Doctrine\ORM\PersistentCollection {#2469 …} +votes: Doctrine\ORM\PersistentCollection {#2467 …} +reports: Doctrine\ORM\PersistentCollection {#2372 …} +favourites: Doctrine\ORM\PersistentCollection {#2386 …} +notifications: Doctrine\ORM\PersistentCollection {#2385 …} +badges: Doctrine\ORM\PersistentCollection {#2378 …} +children: [] -id: 26561 -titleTs: "'api':8 'entiti':4 'lemmi':7 'modlog':3 'question':1" -bodyTs: "'/api/interfaces/modbanview.html](https://join-lemmy.org/api/interfaces/modbanview.html)).':28 'admin':33,59 'anyon':77 'api':68 'appar':74 'ban':31,41 'call':42 'client':11 'display':7 'doc':69 'explain':72 'explan':65 'goe':46 'help':71,78 'hi':1 'inconsist':75 'instanc':30 'instead':60 'issu':39 'item':21,50 'join-lemmy.org':27 'join-lemmy.org/api/interfaces/modbanview.html](https://join-lemmy.org/api/interfaces/modbanview.html)).':26 'light':81 'like':51 'log':20 'm':3 'meanwhil':55 'mod':19 'modaddcommunityview':54 'modaddview':52 'modbanview':25 'moder':43 'modhidecommun':56 'modlog':6 'person':38 'question':17 'quick':16 'regard':18 'requir':32 'right':34 'shed':79 'specif':23 'unfortun':61 'use':58 'view':22,57 'voyag':10 'work':4" +cross: false +upVotes: 0 +downVotes: 0 +ranking: 1704072878 +visibility: "visible " +apId: "https://lemmy.today/post/4732610" +editedAt: null +createdAt: DateTimeImmutable @1704055378 {#2453 : 2023-12-31 21:42:58.0 +01:00 } } |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
4 | DENIED | moderate | App\Entity\Entry {#2363 +user: App\Entity\User {#265 …} +magazine: Proxies\__CG__\App\Entity\Magazine {#2377 …} +image: null +domain: Proxies\__CG__\App\Entity\Domain {#2370 …} +slug: "Question-about-modlog-entities-in-the-Lemmy-API" +title: "Question about modlog entities in the Lemmy API" +url: null +body: """ Hi, I’m working on modlog display for the Voyager client and I have a quick question regarding mod log item views, specifically, the `ModBanView` ([join-lemmy.org/api/interfaces/ModBanView.html](https://join-lemmy.org/api/interfaces/ModBanView.html)).\n \n If instance bans require admin rights, why is the person issuing the ban called “moderator” here?\n \n Same goes for some other items like `ModAddView` and `ModAddCommunityView`. Meanwhile, `ModHideCommunity` view uses “admin” instead.\n \n Unfortunately, there is no explanation in the API docs to help explain this apparent inconsistency. Can anyone help shed some light on this? """ +type: "article" +lang: "en" +isOc: false +hasEmbed: false +commentCount: 2 +favouriteCount: 3 +score: 0 +isAdult: false +sticky: false +lastActive: DateTime @1711238280 {#2454 : 2024-03-24 00:58:00.0 +01:00 } +ip: null +adaAmount: 0 +tags: null +mentions: null +comments: Doctrine\ORM\PersistentCollection {#2469 …} +votes: Doctrine\ORM\PersistentCollection {#2467 …} +reports: Doctrine\ORM\PersistentCollection {#2372 …} +favourites: Doctrine\ORM\PersistentCollection {#2386 …} +notifications: Doctrine\ORM\PersistentCollection {#2385 …} +badges: Doctrine\ORM\PersistentCollection {#2378 …} +children: [] -id: 26561 -titleTs: "'api':8 'entiti':4 'lemmi':7 'modlog':3 'question':1" -bodyTs: "'/api/interfaces/modbanview.html](https://join-lemmy.org/api/interfaces/modbanview.html)).':28 'admin':33,59 'anyon':77 'api':68 'appar':74 'ban':31,41 'call':42 'client':11 'display':7 'doc':69 'explain':72 'explan':65 'goe':46 'help':71,78 'hi':1 'inconsist':75 'instanc':30 'instead':60 'issu':39 'item':21,50 'join-lemmy.org':27 'join-lemmy.org/api/interfaces/modbanview.html](https://join-lemmy.org/api/interfaces/modbanview.html)).':26 'light':81 'like':51 'log':20 'm':3 'meanwhil':55 'mod':19 'modaddcommunityview':54 'modaddview':52 'modbanview':25 'moder':43 'modhidecommun':56 'modlog':6 'person':38 'question':17 'quick':16 'regard':18 'requir':32 'right':34 'shed':79 'specif':23 'unfortun':61 'use':58 'view':22,57 'voyag':10 'work':4" +cross: false +upVotes: 0 +downVotes: 0 +ranking: 1704072878 +visibility: "visible " +apId: "https://lemmy.today/post/4732610" +editedAt: null +createdAt: DateTimeImmutable @1704055378 {#2453 : 2023-12-31 21:42:58.0 +01:00 } } |
||||||||||||||||||||||||
|