• Resolved olexandrman

    (@olexandrman)


    [ Moderator note: moved to Fixing WordPress. ]

    I want that all registered users of my WordPress site could log in to my apart site (asp.net). I installed api Owin.Security.Providers.WordPress to my asp site, and for this api I need CliendId and ClientSecret from WordPress. Where can I get this CliendId and ClientSecret ? I installed OAuth Server plugin and create new user in this plugin. But CliendId and ClientSecret that were generated for user are invalid when I run my asp site. https://snag.gy/gsLBFY.jpg

    • This topic was modified 7 years, 11 months ago by olexandrman.
    • This topic was modified 7 years, 11 months ago by Jan Dembowski.
Viewing 1 replies (of 1 total)
  • Hello,

    I installed and setup up your plugin but when I’m including it into my WP page it returns me these rows:

    While trying to retrieve events, Google returned an error:
    
    Error calling GET https://www.googleapis.com/calendar/v3/calendars/7n0rjrnt1etplqqqapdmplf74o%40group.calendar.google.com/events?singleEvents=true&maxResults=2500&timeZone=Europe%2FRome&timeMin=2017-03-08T00%3A00%3A00%2B01%3A00&timeMax=2018-04-06T23%3A59%3A59%2B02%3A00&key=700942803584-220oupvsg53jq4e73uh1bj0srin4c1to.apps.googleusercontent.com: (400) Bad Request
    
    Please ensure that both your Google Calendar ID and API Key are valid and that the Google Calendar you want to display is public.
    
    Only you can see this notice.

    It seems that your guide about API activation is old compared to the steps I have found now, while setting up my APIs (actually it asks me something related OAuth).
    Should I need to configure everything through the account connected with the calendar I want to get? Because I’m doing all for a client of mine and I have his calendar public, and so far I used my google account to do everything.
    Please let me know how I can manage this issue, thanks in advance!
    Emanuele

Viewing 1 replies (of 1 total)
  • The topic ‘oAuth (CliendId and ClientSecret)’ is closed to new replies.