delta/gitlab/gitlab-ce.git/app/controllers/admin, branch example-java gitlab.com: gitlab-org/gitlab-ce.git Add option to include the sender name in body of Notify email. fix #7824 2016-02-09T11:58:13+00:00 Jason Lee huacnlee@gmail.com 2016-01-26T13:34:42+00:00 9474e36f462522af1804e760e5fe134f101fce08 






Allow limited Markdown in Broadcast Messages
2016-02-06T19:30:07+00:00

Robert Speicher
rspeicher@gmail.com

2016-02-04T04:01:04+00:00

89b3ddd609063d93f39a02279f0f3e23b8b6b364

Closes #11853





Closes #11853







Improve admin broadcast messages page
2016-02-05T15:01:10+00:00

Dmitriy Zaporozhets
dmitriy.zaporozhets@gmail.com

2016-02-05T15:01:10+00:00

989caaebdc698fd1dffd44e01b24f0c420842632

* Show latest broadcast messages first on admin page
* Use nice looking pagination

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>





* Show latest broadcast messages first on admin page
* Use nice looking pagination

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>







Refactor Admin::SpamLogsController to block user before destroying
2016-02-02T13:25:44+00:00

Douglas Barbosa Alexandre
dbalexandre@gmail.com

2016-01-26T21:20:01+00:00

718b1dddfe8d7422e8de8b2fbbd8357fc1c3b5e4












Support Akismet spam checking for creation of issues via API
2016-02-02T13:25:44+00:00

Stan Hu
stanhu@gmail.com

2016-01-09T19:30:34+00:00

d20e75a8d80c2828336cd22897ea6868d666f8a5

Currently any spam detected by Akismet by non-members via API will be logged
in a separate table in the admin page.

Closes #5612





Currently any spam detected by Akismet by non-members via API will be logged
in a separate table in the admin page.

Closes #5612







Partially revert "Add IP check against DNSBLs at account sign-up"
2016-01-28T21:28:19+00:00

Robert Speicher
rspeicher@gmail.com

2016-01-28T21:28:19+00:00

ca05054ea2a8aff81822f310c5dafb68ae26e10e

This partially reverts 6a5cd3ca - we keep the migration and add a new
migration that reverts it in order to keep migration history intact.





This partially reverts 6a5cd3ca - we keep the migration and add a new
migration that reverts it in order to keep migration history intact.







Merge branch 'feature/check-against-rbl-only' into 'master'
2016-01-20T19:24:20+00:00

Robert Speicher
rspeicher@gmail.com

2016-01-20T19:24:20+00:00

1553c560e0d02e670b7cec2b443545e67418b569

Split from !2455

References #9092

See merge request !2515





Split from !2455

References #9092

See merge request !2515







Add IP blocking against DNSBL at sign-up
2016-01-20T14:28:19+00:00

Tomasz Maczukin
tomasz@maczukin.pl

2016-01-20T12:16:34+00:00

8536e083f7b2d7ed77ecae83774d75f68d66e0b4












Add sentry integration
2016-01-18T16:15:10+00:00

Jeroen Nijhof
jeroen@jeroennijhof.nl

2016-01-18T16:15:10+00:00

85e0fce9eee4f20c6c627209828f7351ab0aedae












Merge branch 'feature/ldap-sync-edgecases' into 'master'

2016-01-14T11:00:08+00:00

Douwe Maan
douwe@gitlab.com

2016-01-14T11:00:08+00:00

4d64a32c88dd5f87621d391c0f10f6acef094073


LDAP Sync blocked user edgecases

Allow GitLab admins to block otherwise valid GitLab LDAP users
(https://gitlab.com/gitlab-org/gitlab-ce/issues/3462)

Based on the discussion on the original issue, we are going to differentiate "normal" block operations to the ldap automatic ones in order to make some decisions when its one or the other.

Expected behavior:

- [x] "ldap_blocked" users respond to both `blocked?` and `ldap_blocked?`
- [x] "ldap_blocked" users can't be unblocked by the Admin UI
- [x] "ldap_blocked" users can't be unblocked by the API
- [x] Block operations that are originated from LDAP synchronization will flag user as "ldap_blocked"
- [x] Only "ldap_blocked" users will be automatically unblocked by LDAP synchronization
- [x] When LDAP identity is removed, we should convert `ldap_blocked` into `blocked`
 
Mockup for the Admin UI with both "ldap_blocked" and normal "blocked" users:
![image](/uploads/4f56fc17b73cb2c9e2a154a22e7ad291/image.png)

There will be another MR for the EE version.

See merge request !2242





LDAP Sync blocked user edgecases

Allow GitLab admins to block otherwise valid GitLab LDAP users
(https://gitlab.com/gitlab-org/gitlab-ce/issues/3462)

Based on the discussion on the original issue, we are going to differentiate "normal" block operations to the ldap automatic ones in order to make some decisions when its one or the other.

Expected behavior:

- [x] "ldap_blocked" users respond to both `blocked?` and `ldap_blocked?`
- [x] "ldap_blocked" users can't be unblocked by the Admin UI
- [x] "ldap_blocked" users can't be unblocked by the API
- [x] Block operations that are originated from LDAP synchronization will flag user as "ldap_blocked"
- [x] Only "ldap_blocked" users will be automatically unblocked by LDAP synchronization
- [x] When LDAP identity is removed, we should convert `ldap_blocked` into `blocked`
 
Mockup for the Admin UI with both "ldap_blocked" and normal "blocked" users:
![image](/uploads/4f56fc17b73cb2c9e2a154a22e7ad291/image.png)

There will be another MR for the EE version.

See merge request !2242