Force admin contact configuration.

[leonjza]

See eve-seat/seat#429 for more information.

[regner]

I was asked to chime in here. Essentially what we are seeing on our side is most users don't have a proper email address setup in the user agent. Here is a sample from over the last 24 hours:

  userAgent                                                  count   percent
    PhealNG/2.3.4+eveseat/[email protected]   2310817 33.207582
    PhealNG/2.3.4+eveseat/[email protected]   1628843 23.407279
    PhealNG/2.3.4+eveseat/[email protected]     363219  5.219636
    PhealNG/2.3.4+eveseat/1.0.10+****@****.com                361250  5.191341
    PhealNG/2.3.4+eveseat/1.0.12+****@****.com                319359  4.589347
    PhealNG/2.3.4+eveseat/1.0.11+****@****.com                289840  4.165144
    PhealNG/2.3.4+eveseat/1.0.11+****@****.com                201905  2.901475
    PhealNG/2.3.4+eveseat/1.0.12+****@****.com                159709  2.295097
    PhealNG/2.3.4+eveseat/1.0.12+****@****.com                154763  2.224021
    PhealNG/2.3.4+eveseat/1.0.12+****@****.com                134392  1.931279

This isn't so bad, but there have been several instances where that count would be around the 7m mark. I would like to contact the person responsible for that instance and discuss some things instead of banning them.

[leonjza]

Thank you. While you showing some stats, Im super curious about top 0 src-ip :P (masking the actual ips ofc).

As for the problem at hand, a change will be going in forcing an update of the admin email for CCP's use.

[MilosRasic]

@leonjza are you saying you don't have access to the super secret SeAT dial home db? :D

[regner]

Ask and you shall recieve @leonjza. Here are the top IPs for the last 24 hours. Used the following Splunk query: index = api UserAgent = "PhealNG/*+eveseat/*" | top clientIP

    *.*.*.*    1270691 18.229540
    *.*.*.*     677351  9.717388
    *.*.*.*     634327  9.100158
    *.*.*.*     360421  5.170658
    *.*.*.*     349545  5.014629
    *.*.*.*     320324  4.595420
    *.*.*.*     291888  4.187473
    *.*.*.*     274699  3.940877
    *.*.*.*     258335  3.706116
    *.*.*.*     215651  3.093764

[leonjza]

@MilosRasic sure, if only such a thing existed.
@regner thanks :)

[leonjza]

Users will be required to set the admin contact now in the next web release. A warning and log entries will appear about this.

[warlof]

bumping this issue as it appears contact information is never pass to the eseye user agent
as a result, ccp had no way to track about instance owner since years

waiting about a feedback from them regarding the ability to submit client_id instead of an e-mail address which looks more gdpr compliant - and perhaps more useful on their side.

[soratidus999]

https://docs.esi.evetech.net/docs/esi_introduction.html#user-agent:~:text=When%20making%20requests%2C%20it%E2%80%99s%20recommended%20you%20set%20a%20User%2DAgent%20header%20in%20your%20client%20which%20includes%20the%20source%20of%20the%20request%20and%20contact%20information

The docs call for Contact Information, But keep in mind this, and other identifying information is stripped on the load balancer before its passed to ESI and/or the monolith