-
Notifications
You must be signed in to change notification settings - Fork 54
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
admin role did not assigned correctly on 1.3.0 #37
Comments
Sorry about that @ferrari! @ceci-woodward as the person who submitted the PR, cane you support this? Any thoughts what the issue might be? @ferrari I'm not using hubot-auth right now, so I'm not that useful here. If we def can't resolve it, and it seems a legit issue that others will hit, I'd consider reverting the changes. (but hopefully not!) |
@ferrari Can you let me know what OS and Adapter you're using? |
I'm having similar issues where the values set in HUBOT_AUTH_ROLES aren't being picked up in 1.3.0. I'm using the Slack adapter on CoreOS (Docker container in Kubernetes.) |
thanks for chiming in @ceci-woodward! if you don't have time to investigate these things this week, please make sure to let me know, and I can do a temporary revert until such a time that you have bandwidth to check it out :) |
@ceci-woodward |
I got similar problems using
|
This pull resolves the issue for me #41 |
Running in to this issue too and think the issue is in the hubot-redis-brain module. I am on hubot-redis-brain@0.0.3 I have my ID in the environment variable In hubot-auth/src/auth.coffee after line 56 I added lines to show my roles.
in hubot-redis-brain/src/redis-brain.coffee at line 48 I added the same before and after the redis merge
The results show that I have the expected roles before the merge but not after
|
That last post was a little misleading. The issue is not in hubot-redis-brain. hubot-redis-brain calls Just added an issue to hubot: hubotio/hubot#1219 |
@patcon I'd recommend just reverting the commit. The given functionality doesn't really work in the case of hubot-auth due to how the roles are stored we need to have the user defined first. |
Oy. Ok, I've been MIA and feel pretty badly about this. I take full responsibility here. I'm going to revert the breaking commit, and so that this sort of thing doesn't get blocked on me again (because, as I said, i'm not using hubot-auth right now), I've given @ceci-woodward write access to the repo |
@ferrari Can you verify if this is still an issue? |
After upgrade from 1.2 to 1.3, admin role seem not work correctly.
I try both new variable
HUBOT_AUTH_ROLES="admin=USERID"
and old oneHUBOT_AUTH_ADMIN=USERID
and both not work.bot always return
There are no people that have the 'admin' role
, I do see the log message showWARNING The HUBOT_AUTH_ADMIN environment variable has been deprecated in favor of HUBOT_AUTH_ROLES
and both variable should still support on v1.3 (after I trace the source code).Any advice? Thanks
ps: I works perfect after I downgrade to v1.2.
The text was updated successfully, but these errors were encountered: