1C:Enterprise platform integration capabilities and techniques

#1
People who like this: 0 Yes / 0 No
Just came
Rating: 1
Joined: Jul 31, 2024
Company:

Hi All!

We want to access to our 1C (client authentication) using our microsoft 365 accounts.

What we done:

1) On azure side we have created an application, gave authority (mail, openID, profile, user read - and also "Granted Access"), entered redirect url (https://<<server name>>/<<publication name>>/authform.html) etc.. (there is no problem on this side)

2) Changed the "default.vrd" file (we had that file before, becouse we were using the web-client). Entered the datas from azure app (client ID, tenant ID, secret ID, redirect URL etc..). The *.vdr data is below:

<openidconnect>
  <providers>
       <![CDATA[
        [
           {
               "name": "azure_oidc",
               "title": "OIDC 1C (Azure)",
               "discovery": "https://login.microsoftonline.com/****************/v2.0/.well-known/openid-configuration",
               "authenticationClaimName": "upn",
               "clientconfig": {
               "authority": "https://login.microsoftonline.com/********************/",
               "client_id": "***********************************",
"client_secret": "**************************",
               "redirect_uri": "https://<<server name>>/<<publication>>/authform.html",
                   "scope": "openid",
                   "response_type": "id_token",
                   "filterProtocolClaims": false,
                   "loadUserInfo": false,
                   "resource": "*****************************"
               }
           }
       ]]]>
   </providers>
   <allowStandardAuthentication>true</allowStandardAuthenticati­on>
</openidconnect>

When trying to connect to 1C (web client) it asks, which authentication mathod we want to use, we choose the "azure", after entering microsoft365 account datas (user name and password), the authentication on azure side is success (we can see it in logs on azure side), but we couldn't login to 1C, we get the page (adding the screen of page in attached file) and doesn't go any further, turns on the same page.

We fount some manuals in internet, did the same. But I thing, that in maybe some additional settings on 1C:Enterprise side.

The version of platform is: 8.3.16.1063

If someone had done client authentication via azure AD, can you please share information and help us :)
Thank you

 
#2
People who like this: 0 Yes / 0 No
Just came
Rating: 0
Joined: Sep 12, 2024
Company: YETEV

Hi,

I am having the same problem. I followed the instruction below.


https://its.1c.ru/db/metod8dev#content:5972:hdoc:azure_provider_settings

There is no problem in integrating with Entra ID. Could there be a problem with the 1C version?  The option to log in via Entra ID is available. After passing this stage, a rotating icon remains on the 1C screen. At this stage, when another user tries to access 1c, they encounter the rotating screen of 1c.

The version of platform is: 8.3.16.1063
Appache version: 2.2.22

Download 1c_01.png (15.15 KB)
 
#3
People who like this: 0 Yes / 0 No
Just came
Rating: 1
Joined: Jul 31, 2024
Company:

Hello!

Nobody replied to my message...
but, we solved it ourselves. The problem was in platform version. In documentation it says that platform version 8.3.15 (and above) it OK for authentication with microsoft 365 accounts...but its not enough. we updated platform to 8.3.23.2236 version, and the problem solved itself..didnot do any extra thing.
If anyone have the same situation, just update your platform version (at 8.3.23 it works correctly)

 
#4
People who like this: 0 Yes / 0 No
Just came
Rating: 0
Joined: Feb 7, 2026
Company:

Oh thank you for this post

 
Subscribe
Users browsing this topic (guests: 2, registered: 0, hidden: 0)
Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.

/* --- ФИКС ЗАГОЛОВКОВ ДОКУМЕНТАЦИИ (BRUTE FORCE) --- */ /* Цепляемся за все возможные контейнеры Битрикса */ .content h1, #content h1, .workarea h1, .content h2, #content h2, .workarea h2, .content h3, #content h3, .workarea h3, .content h4, #content h4, .workarea h4, .content h5, #content h5, .workarea h5, .content h6, #content h6, .workarea h6 { display: block !important; font-weight: 700 !important; color: #222 !important; text-transform: none !important; margin-top: 1.5em !important; margin-bottom: 0.5em !important; line-height: 1.2 !important; } /* Явно задаем размеры, чтобы перекрыть "font-size: 100%" */ .content h1, #content h1 { font-size: 28px !important; } .content h2, #content h2 { font-size: 24px !important; } .content h3, #content h3 { font-size: 22px !important; } .content h4, #content h4 { font-size: 20px !important; } .content h5, #content h5 { font-size: 18px !important; } /* Ваш случай (5 решеток) */ .content h6, #content h6 { font-size: 16px !important; } /* Если Битрикс или редактор засунули внутрь h5 тег span или font */ .content h5 *, #content h5 *, .workarea h5 * { font-size: inherit !important; color: inherit !important; font-weight: inherit !important; } /* --- СТИЛИЗАЦИЯ ТЕКСТА (Markdown Style) --- */ /* Ссылки в тексте делаем более заметными */ .content a:not([class]) { color: #005aa0; text-decoration: none; border-bottom: 1px solid rgba(0, 90, 160, 0.2); } .content a:not([class]):hover { border-bottom-color: #005aa0; } /* Списки (чтобы не прилипали) */ .content ul, .content ol { margin-bottom: 15px !important; padding-left: 20px !important; } .content li { margin-bottom: 5px !important; }